Related
READ FIRST
Hey,
Welcome to this tut. It's been active for a few months now but there are some things many users and the dev's want to tell you.
1. DO NOT ask questions about when things are finished.
2. Before you ask an question use the SEARCH THIS THREAD button
3. Post tut related questions in THIS THREAD, so do NOT POST QUESTIONS IN THE DEV THREAD
4. Use the THANKS button when you get your answer.
5. Don't ask questions like "I've done everything but it doesnt work" we really can't help you with such a question cause we don't know where what goes wrong..
If your post is violating one of these "thread rules" (don't call then real rules...) then we'll just report your post. getting it deleted.. etc. etc..
For our "Wise" users here (i mean the ones who actually READ before they post) Don't go flame on users asking stupid questions just leave them allone and REPORT the post
Thanks & Enjoy.
ShadowAS1
Okay, to be clear. All this work is COPYRIGHTED By the devs, The TUT is copyrighted by me, so stop frigging CopyPastaing my tut.. . With other words.. ASK PERMISSION TO DO SO, Thanks[/B]
New in this update:
Added new FOTA
Disclaimer:
This stuff is still experimental, me, nor the devs will be responsible for any damage done to you, your phone or whatsoever, so USE AT OWN RISK
Warning:
Do NOT flash when you don't know what you're doing. It could BRICK your phone. And I will NOT support it when you screw up your phone.
FAQ
Q: It doesn't work I've done everything but it doesnt work
A: Do you even think we CAN answer the question if you ask it like that?
Q: My phone shuts down after 2 minutes, why?
A: It's an idle bug.. We're still looking for a solution
Q: When will GB be released, When will the modem drivers be finished.. etc..
A: WE DON'T KNOW! STOP ASKING THIS
What WORKS in this build
WiFi (+dhcp)
Market
3D Games (some maybe not)
Launchers (tested TWLauncher, Zeam, LauncherPRO)
Audio (FULL Working now)
Video's (see my livestream.com example)
What does NOT work in this build
Modem (3G, Calls, ETC) (works partially on oleg's build we're still working on it)
Idle time (also known as the shutdown bug)
Sensors (Causes battery bug)
Supported BOOTLOADERS
S8500DDJE7_MAY
S8500JVKC1_MAR
S8500XXJD9_APR
S8500XXJEE_MAY
S8500XXJEF_JUN
S8500XXJF1_JUN
S8500XXJF4_JUL
S8500XXJH2_DEC
S8500XXJH2_NOV
S8500XXJH3_AUG
S8500XXJI3_FEB
S8500XXJI3_NOV
S8500XXJID_SEP
S8500XXJK2_MAY
S8500XXJL2_APR
S8500XXJL2_DEC
S8500XXJL2_MAR
What do we need?
Multiloader: MegaUpload
zImage & stuff: MegaUpload
EXT2 IMG Filesystem: Part1 Part2
FOTA: MegaUpload (Restored old one)
Ok before we start. The tutorial is now 100% Rewritten. But you still need to read carefully
Notice
Clean out your ENTIRE bada storage first cause we will need almost everything of it
Notice2: This project is still in ALPHA Stage. So don't expect a fully awesome working version yet.
In this version all KNOWN fixes are implented except for root
1. Download all the needed files, when you've done so extract the ZIP with the zImage stuff in it and place it in you bada storage root. (you can extract the .001 with 7-zip)
(i made the Images URLS's because they're to big)
1b. Connect your phone and put it in Mass Storage mode
You should copy your files like the Images below
Bada Storage root:
http://ShadowAS1.com/badadroid/storageroot1.png
This should be inside your storage root:
http://ShadowAS1.com/badadroid/storageroot2.png
This should be inside your galaxyboot folder:
http://ShadowAS1.com/badadroid/storageroot3.png
So inside the sorage root should be your galaxyboot folder and the makext2img.sh
inside the galaxyboot folder should be zImage, SBL.bin and the .IMG file
2.Then you should shut down your phone and boot it in download mode:
Vol Down+Camera+Power and you will see DOWNLOAD MODE on the screen
3.Open up multiloader and take over my config here:
http://shadowas1.com/badadroid/multiloader.png
When you click port search the name "LISMORE" should/can popup next to the right COM port
Now click download and wait for it to finish
Okay, now your phone is ready for the first android run
Boot it by holding power+menu+vol up: (see image)
http://shadowas1.com/badadroid/IMG_0052.JPG
Then this should popup (after the SGS screen)
DO NEVER, ABSOLUTELY NEVER PULL OUT BATTERY OR TOUCH THE PHONE IN THIS PROCESS
http://shadowas1.com/badadroid/IMG_0050.JPG
This can take up to 5 minutes.
Now, Two things can happen
1. The phone boots bada
2. The phone shuts down
In any of this cases your phone is absolutely fine. If you have case 2 you can boot bada to check if everythings alright if you wish.
Assuming we all boot bada shut down the phone again
Boot android in the normal way by holding the Power and Call key
=====Removing Android from your bada partitions======
On request i add this one, In order to remove all android stuff put the "mkext2images-remove.sh" in your bada storage root and boot recovery mode again
Goodluck, ShadowAS1
Good Luck,
ShadowAS1
_________________
Changelog:
12-7(2): Added new FOTA
12-7: Added what (doesn't) work(s) list
10-7: Updated some stuff (FW list)
Thanks a lot!!
Great Guide!
But!
If some of you are having problems installing VMware due to processor requirements, we can still use the Ubuntu live CD and use gparted disk utility..
Also, we can also use a live CD version of gparted.. just search it at Google..
Wonderful guide to read, testing it now. Will post my results if i manage it (or not )
Regards
So can i use other apks than that specified above..?
prok**** said:
So can i use other apks than that specified above..?
Click to expand...
Click to collapse
The APKs listed above are ment to avoid crashing
you can use al programs listed in the phone i can not guarantee that it will work completely this is still pre-alpha
Nice guide...thank you
Hi!
I have followed all the steps.
Now I'm in the First-time Run section and when I start Android (end call and then start call buttons) the screen flashes, then the Galaxy S screen appears. After 6-7 seconds, blank screen and... Samsung Wave and Bada screens with bada startup!
I saw other member in other post having the same issue, but he had still no answer.
Any idea?
Yeap, still same problem as mcmollo after following this guide as well ...
Works for me
Thanks
ShadowAS1 said:
The APKs listed above are ment to avoid crashing
you can use al programs listed in the phone i can not guarantee that it will work completely this is still pre-alpha
Click to expand...
Click to collapse
i see .. well if i try i ll let u guys know.. .. thank u for ur support.. still waiting for ubuntu..
Same here
You guys are on xxjl2 firmware right?
kadavil said:
You guys are on xxjl2 firmware right?
Click to expand...
Click to collapse
Yeah, as stated in your and in Shadow's guide.
Yeap, same here: XXJL2 provided in the tutorials.
I have a SanDisk 2GB class 4 microSD card and created a FAT16 primary partition (1GB) and a EXT2 primary partition (1GB).
kadavil said:
You guys are on xxjl2 firmware right?
Click to expand...
Click to collapse
Yes. I repeated the tutorial 3 times, taking care of doing it exactly as you say. But Bada still loading after Galaxy screen.
Maybe compatibility problem with the SD card?.
Mine is KINGSTON MICRO SD HC 8GB CLASS 4
I created a FAT16 primary partition (4GB) and then the EXT2 partition (4GB).
Will we install waveII (s8530) ?
SORRY SORRY I forgot something important. Read the tuto again. you'll notice the edit (because there's abig fat "EDIT" in front of it) This may fix the problems
can i use ubuntu 10.04?
ShadowAS1 said:
SORRY SORRY I forgot something important. Read the tuto again. you'll notice the edit (because there's abig fat "EDIT" in front of it) This may fix the problems
Click to expand...
Click to collapse
thanks, i hope, we ll use stable android on 8530...
If you just switched from iPhone or BB or this is ur first android. Read this thoroughly and see ur questions get eliminated by this guide. if you find this helpful than show your appreciation and hit that thnx button.
I don't take any credit I Googled everything. I do take credit of modifying some stuff in word. I won't have this Phone but I am just being helpful to the community.
Little in-depth information about Android. Must Read. Thank You Pirateghost.
Pirateghost said:
Android itself is OPEN. you can go and build your very own version of 4.0 ICS right now from source code. there are very few phones you can STABLY and RELIABLY run it on though.
The NEXUS line of phones exists for a reason. they are untouched by carriers (verizon teabagged the Galaxy Nexus a little), and do not have some stupid overlay on them. they are developer devices in that it is the first phone to get android updates straight from google (no manufacturer interference required).
every other phone is tainted with a manufacturer's UI. Touchwiz on Samsung phones (galaxy nexus is a samsung but they provided the hardware not the software), Sense on HTC, 'non-blur' on Motorola, whatever Sony calls theirs...lol, LG, etc
on top of that tainted Android interface is a carrier branding or lockdown (doesnt apply to the entire world, but im only referring to US here)
so google releases new version of Android
manufacturers build phone, and customize android to fit their model (this is where android almost stops being OPEN)
carriers get a hold of the manufacturers build of android and tweak and modify it themselves (more than likely they just tell the manufacturers what they want), as you know they love to include bloat and lock it down from the user
you receive your android phone after it has gone through all those steps....long process huh? we dont get updates to newer versions as quickly because of that long process...and they would rather us buy new phones instead of improving perfectly good hardware.
Android is open in the sense that manufacturers can use it however they wish, within reason. it is not necessarily meant to be 'open' to the average end user, and manufacturers dont want you messing with the phone they built. its the reason XDA is what it is today, albeit with roots deep in WinMo hacking.
Click to expand...
Click to collapse
ADB → Android Debug Bridge (adb) is a versatile command line tool that lets you communicate with an emulator instance or connected Android-powered device..
Android →Unveiled on 5 November 2007, Android is a mobile operating system running on the Linux kernel developed by Google.
AOSP → Android Open Source Project
Apps2SD → Move applications from the internal NAND memory on the device to a removable SD Card.
BLN → BackLight Notification
Bloatware → Software bloat is a process whereby successive versions of apps include an increasing proportion of unnecessary features that are not used by end users, or generally use more system resources than necessary, while offering little or no benefit to its users. Like all the crap that comes from At&t
Brick → When used in reference to consumer electronics, "brick" describes a device that cannot function in any capacity (such as a device with damaged firmware). This usage derives from the fact that some electronic devices (and their detachable power supplies) are vaguely brick-shaped, and so those which do not function are useful only as actual bricks. The term can also be used as a verb. For example, "I bricked my phone when I tried to modify its firmware."[
Hard Brick → When your phone does not turn on at all. When you can’t get in to CWR/CWM Or Stock recovery. You are basically screwed.
Soft Brick → When your phone bootloops. When you can get into CWR/CWM. When You can use jigtag to get into download mode.
Busybox → BusyBox provides several stripped-down Unix tools in a single executable. It runs in a variety of POSIX environments such as Linux, Android, FreeBSD and others, such as proprietary kernels, although many of the tools it provides are designed to work with interfaces provided by the Linux kernel. It was specifically created for embedded operating systems with very limited resources. Platforms counterparts, but they are pretty close and useful nonetheless.
CWR OR CWM ClockworkMod Recovery →A custom recovery for Android phones and tablets that allows you to perform several advanced recovery, restoration, installation and maintenance operations on your Android device that aren’t possible with the stock recovery.
DEODEX → Apk files have respective odexes that devs use to supposedly save space. Deodexing means you convert it back to a .dex file and put it back inside the apk. This allows you to easily replace file (not having to worry about odexes), but the main point was to deodex services.jar so that you can change all text to different colors (such as the clock color to white) and to deodex services.jar, you need to deodex everything.
Flashing → The process of applying a firmware image (or ROM) to a device. It generally entails a very specific order of steps. Failing to complete any one of these steps properly may result in bricking the device.
Firmware → is a term often used to denote the fixed, usually rather small, programs and/or data structures that internally control various electronic devices. Programs stored in the ROM, EPROM, or flash memory that usually control various internal electronic devices (Hard Drives, Keyboards, Displays, etc). Firmware is typically 'fixed' software that is not updated in consumer devices, however it is often updated (or 'flashed') by advanced users to fix bugs or add features to the device. Flashing firmware designed for one device onto a different device, or not following a specific procedure while flashing will often render the device unusable.
Kernel → is the main component of most computer operating systems; it is a bridge between applications and the actual data processing done at the hardware level. The kernel's responsibilities include managing the system's resources (the communication between hardware and software components
Radio → The cellular radio on the device which needs control software called firmware to control it.
ROM → Read Only Memory. In the context of an Android device, ROM is the internal flash memory where the core operating system resides. It can also refer to a specific version firmware that can be applied to a device through a process usually referred to as flashing. An improperly flashed ROM can often brick the device, rendering it unusable.
Superuser→ A program, which gives unlimited access privileges to perform any or all operations on the operating system.
ODIN → Odin is the Samsung software used to update Samsung phones. It does not work with any other devices other than official Samsung phones.
OTA or FOTA → (F)OTA stands for (Firmware) Over The Air and is the process by which required updates and enhancements to your phone's basic operating system can be sent to you through the cellular network. The Galaxy S II software update will be sent via FOTA and is available through Samsung Kies mini.0
ODEX → In Android file system, applications come in packages with the extension .apk. These application packages, or APKs contain certain .odex files whose supposed function is to save space. These ‘odex’ files are actually collections of parts of an application that are optimized before booting. Doing so speeds up the boot process, as it preloads part of an application. On the other hand, it also makes hacking those applications difficult because a part of the coding has already been extracted to another location before execution.
SDK → Software Development Kit.
Logcat → A debugging tool built into Android devices that displays system logs as they occur. See Logcat.
NANDroid → A set of tools that will enable anyone who has root on their Android device to make FULL system backups, in case something goes wrong or you want to try out that new experimental ROM/theme. NANDroid will backup (and restore) /system, /data, /cache, and /boot partitions.
Recovery Mode → A special environment that you can boot into for troubleshooting and upgrading purposes.
Kang → The process of creating a code based of someone else's code or reapplying code that someone else created into your own code (e.g. git cherry-pick)
Rooting → is a process that allows users of mobile phones and other devices running the Android operating system to attain privileged control (known as "root access") within Android's Linux subsystem with the goal of overcoming limitations that carriers and manufacturers put on some devices.
How to Root Your note????
There are two root methods for YOUR ATT GALAXY NOTE!
1 which uses kernel to root.
2 This one flash with Odin but in system level not boot kernel.
#1 root by Da_G!
Da_G said:
Hi!
This kernel enables custom boot animations (/system/media/sanim.zip), adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter, which is presumably used by Samsung as a reason to decline warranty service (not aware of any reports of this occuring yet...?)
Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Click to expand...
Click to collapse
#2 Root by mashi!
How to backup your current ROM????
Hard Way!
Get into CWR!
Scroll down to backup and restore!
Press backup.
How to Restore Your backup????
If You used ROM manager than!
Go to manage and restore backups!
And press the one you like to restore!
If you have Nandroid than!
Go to CWR!
Scroll down to backup and restore!
Press restore!
How to Flash a ROM????
Basic Steps
! Choose the ROM that you want and download its .zip file
!! Transfer the zip file to your phone’s sd card. Do not put it into any folder.
!!! Turn off your phone and reboot into recovery, usually by holding the down button and power button at the same time.
!!!! Do a Nandroid backup
!!!!! Wipe the phone 3 times by clearing cache/factory restore 3 times and wiping dalvik cache and system format
!!!!!! Flash the zip file that you put on your sd card
!!!!!!! Reboot phone
You can find all ROMS here!
How to flash Kernel with CWM????
_Download the Kernel You want to flash and put it in sd card.
__Boot in to CWM!
___Wipe cache & Dalvik Cache
____Press install from Sd card!
_____Select the kernel that you dloaded!
______Flash it!
_______Reboot!
________Check in CPU SPY to see if you successfully flashed Kernel.
You can find Kernels in development forum.
These will set you back to Stock and Unroot Your phone.
Da_G said:
Hi,
This is an odin .tar prepared with the stock AT&T Kernel, System, and Recovery.
Flash it from odin using the same instructions as my root thread
After flashing, you may need to boot into recovery by powering off, holding vol up + vol down, and holding power until you get into recovery. Then perform a factory reset, this should get you up and running after most brickery.
Note that this is a large file (~450MB), please spare my web host if you don't particularly need it
Download .rar here
Below are stock kernel-only odin tars:
AT&T stock kernel-only odin pda tar
TELUS stock kernel-only odin pda tar
Bell stock kernel-only odin pda tar
Rogers stock kernel-only odin pda tar
Don't forget the donate link in my signature if you find this useful
Click to expand...
Click to collapse
Very cool thank you! I will finally be upgrading from an iP 3G!
LOL . . . . ever since I got it no phone really wowed me until I saw the G Note in November. Anywhoo. . . I was hoping for a noob friendly guide like this
appdroid said:
reserved 1
How to Root Your Skyrocket????
Click to expand...
Click to collapse
Not sure why do i need to know how to root the Skyrocket for the ATT Note here? just saying
Sry just fixed it.
sweetboy02125 said:
Not sure why do i need to know how to root the Skyrocket for the ATT Note here? just saying
Click to expand...
Click to collapse
look at you go! haha good work !!!
I figure this is the least i can do to help young community here!
00mred00 said:
look at you go! haha good work !!!
Click to expand...
Click to collapse
tx appdroid, us noob's really appreciate it!
(in all my years i never seen the "Reserve" post idea b4...it was a DUH moment for me lol)
Excellent guide for us that are really green on the Android platform.
thank you for helping this noob
appdroid said:
I figure this is the least i can do to help young community here!
Click to expand...
Click to collapse
I'm just so young and I need your help
How do you permanently change the hostname on Android?
On CyanogenMod ROMs this is easy, there was an option for it in Applications -> Development Options. But I don't know what hooks that uses and I don't know how to do it on this flavor of Android we have.
Thanks for your post, it help me a a lot. I done a little scripting on unix using mostly tcl. I hope I can get back on it and develop a few applications for this phone once I have it on march.
Thanks!
Thanks for the noob thread. Switched over from an iP4 and its taking a little getting used to. Luckily I already had the Revue and TF101 to help a little.
On a side note I found the http://forum.xda-developers.com/showthread.php?t=1505062 root method was very easy and didnt involve the counter getting screwed up or having to flash a whole new rom. Highly recommend it for anyone just wanting to root their device.
ANother Android Newbie
Coming from IP4 and looking forward to learning hot to make Android work for me.
How do I read your "Reserveds"???
I never tried S8500 Android, nor I have experience with Android handsets...
But I have stupid Questions.
Feel free to correct me, if I'm too stupid.
1.
I have never seen "optimized" aka custom ROMs...
Why?
Is it not possible to remove few Sounds, Pics... config files?
Maybe edit few settings...
2.
What is with such funny and normally easy tasks like this...
Some Logo or maybe start Animation or something like this:
http://forum.xda-developers.com/showthread.php?t=1396818
3.
Please read now carefully or ignore it.
Your choice.
Everyone is welcome to post something usefull...
if not usefull... who cares...
Free speech for everyone.
Best Regards
P.S.:
I'll start soon with Download files... and check few things...
As I am Android MEGANOOB.
1. Kernel is not ready so it is harder to make a ROM
2. The boot animation is a minor thing. The most important is to make android working on Wave I and II. Maybe after the devs would choose a boot animation.
1. Kernel is not ready so it is harder to make a ROM
2. The boot animation is a minor thing. The most important is to make android working on Wave I and II. Maybe after the devs would choose a boot animation.
Click to expand...
Click to collapse
At the moment our Porting "Gods" not talk anymore with as stupid groupies...
I am not dumb enough to wait ... wait...
Why not use time to learn something.
I will starting now with lesson 1.
I will teach myself.
Attention. Lesson 1.
Downloading file from Internet... You need any space on HD and Browser...
Lesson 2.
After 10000 seconds I found this file:
ext2system.zip
Impossible task.
Zippo I know, but what is ZIP...
Sounds like .trip...
Oh, found something to decompress...
ZIP
WinRAR
Lesson 3.
New file ext2system.img
What I need to open this file...
Thanx in advance...
Best Regards
Okay, this time no joke...
How to extract *.img
Maybe this?
http://forum.xda-developers.com/showthread.php?t=1132724
Need some time for learning...
Best Regards
There is very useful page where You can check file formats and how to open it :
fileinfo . com/extension/img
Maybe you dont have to open img files.
http://forum.xda-developers.com/showthread.php?t=1212616
you can find all the files inside the img files in this thread hopefully. If the links still works.
adfree said:
Okay, this time no joke...
How to extract *.img
Maybe this?
http://forum.xda-developers.com/showthread.php?t=1132724
Need some time for learning...
Best Regards
Click to expand...
Click to collapse
You just have to mount it under linux (something like mount -t ext2 -o loop whatever.img /some_folder). It's an ext2 filesystem image.
But without the working kernel you can't do much... You can change the boot animation (it's stored in the system.img), or the boot logo with some tricks (you have to trick here as the bootlogo comes from the kernel, but it's pretty easy to change).
What do you want to acheive?
What do you want to acheive?
Click to expand...
Click to collapse
Good question...
I want to see files inside to analyze... learning.
This is what I do since 2006...
Playing with Firmware...
Maybe Android is cool...
NO idea yet. As no Android handset in use nor Linux on my PC...
But why not use time...
I am not smart enough to have enough Coding skills...
But my butt is fat enough... waiting for something is not really an option.
Best Regards
As Windows Fanboy maybe I'll try this...
http://www.howtoforge.com/access-linux-partitions-from-windows
Best Regards
My fault...
WinHex can extract files from ext2system.img
Later more...
Best Regards
as I've said many times, you can MOUNT the ext2system.img file from a Linux system using the following:
mount -o loop ext2system.img /some_dir
kind of same principle as here, except it's ext2 filesystem and not samsungs moronic rfs:
http://forum.xda-developers.com/showthread.php?t=751827
when working with android it's definitely preferable to do so on a Linux system, suggest you try installing Ubuntu on a Virtual machine.
I guess the reason a bunch of custom roms haven't popped up is because the lack of modem drive means they don't make it more useful, and we still have no idea how to solve problems like the sleep-power off or microphone crash.
If you want to have a go at modifying it however, the contents of the ext2system.img file are mostly from the I9000XXJPX firmware's "factory.rfs" file image, and many modifications that can be done to that (which is froyo 2.2 based) can possibly be made to work with this one.
note: do not attempt to use the recovery system for any of the "update.zip" packages available
I can see *.qmg Pics...
Are there any Viewer for Android?
I mean any Tool to see *.qmg on PC?
Interesting...
Around 1000 files in 50 folder...
biggest file is Swype.apk with 10 MB...
libicudata.so is with 6 MB biggest .so file in lib folder...
.so are ELFs...
Hmmm...
First I would remove Sounds...
Btw... few Fonts... in ttf...
Hmmmmm.... maybe first would be around 50 MB reduce...
Best Regards
adfree said:
Hmmmmm.... maybe first would be around 50 MB reduce...
Best Regards
Click to expand...
Click to collapse
But why do you want to remove stuffs from it? It's just storage space... I think you'd better install the SD based "release" on your Wave, it's easier to experiment with it. But I totally agree with nbates66: you will need Linux at some point to progress. I have Ubuntu in VirtualBox to tinker with Android.
the ".so" files are kernel module drivers(I am incorrect here, ".ko" files are kernel modules, ".so" files are some form of library), ".apk" files are android applications. The contents of .apk's can be extracted by using an archiver, I just checked using 7-zip.
".qmg" files are basically some sort of animation graphic, you can see them in /system/media/ for battery animation, and boot animation, there is nothing new here it has all previously been modified to death on the 100's of other android devices and most mods done for a Galaxy i9000 Froyo 2.2 firmware should be workable for this one.
you can also clearly see the shutdown animation stored as a set of .png files at /system/media/video/shutdown
the various audio files are all in the .ogg format in audio.
the 4 files inside "/system/firmware" are firmware files for a Galaxy i9000 camera NOT FOR A WAVE S8500 camera!!!
the bootsound and various settings are stored in "/system/etc"
"/system/bin" has various executable files used by the system, though they all are symlinked from "toolbox", this includes things like mv (move file), rm (remove file), and also executables for tasks during boot and handling wifi like "bootanimation" or "playlogo" and "dhcpcd"
if you really have to look at it from within windows, I believe Winimage can extract the contents of ext2system.img.
EDIT: wrong on ".so" files
".qmg" files are basically some sort of animation graphic, you can see them in /system/media/ for battery animation, and boot animation, there is nothing new here it has all previously been modified to death on the 100's of other android devices and most mods done for a Galaxy i9000 Froyo 2.2 firmware should be workable for this one.
Click to expand...
Click to collapse
I need only way convert from qmg into JPG or PNG...
QMG-->JPG
Reason is very simple in my eyes.
the ".so" files are kernel module drivers,
Click to expand...
Click to collapse
Hmm. Maybe now more clear... if folder is named lib like library.
Then these are only parts... like DLL in Windows world...
Btw...
"Surprise". QMG and *.so also exists in bada world...
About *.so...
Are these proprietary Samsung stuff?
Or open source...
Maybe then we could more understand, what is for what...
But why do you want to remove stuffs from it? It's just storage space...
Click to expand...
Click to collapse
Why not... nobody will die or explode.
1.
Train my little brain
2.
Removing unnessary crap can help to free more RAM or other memory...
This is no secret.
3.
XDA is for sharing knowledge and to learn something usefull.
Not only download, without asking why...
Best Regards
adfree said:
I need only way convert from qmg into JPG or PNG...
QMG-->JPG
Reason is very simple in my eyes.
Click to expand...
Click to collapse
well i'm afraid I don't know how to open the QMG's themselves, but all they contain are some sort of animation, the "playlogo" and "playlogos1" executables appear to be something non-standard Samsung created for their boot animations, to use custom animations I believe the workaround used is to rename the playlogos file to something else, and in it's place put a file that points to the android standard "bootanimation" executable, the bootanimation executable plays a boot animation from the "bootanimation.zip" file which is just a zip file with a set of images and a txt file that describes how it should play
here is some info regarding the bootanimation.zip: http://android.modaco.com/topic/338...nimationzip-futurama-bender-bootanimationzip/
adfree said:
Btw...
"Surprise". QMG and *.so also exists in bada world...
About *.so...
Are these proprietary Samsung stuff?
Or open source...
Maybe then we could more understand, what is for what...
Click to expand...
Click to collapse
well the QMG format I believe is some proprietary Qualcomm format (the modem in Wave phones which happens to be Qualcomm can be used for processing of various formats) but the (INCORRECT INFO).so file extension is used across a variety of systems for kernel driver extensions, and .so's are used in this case and for many android devices to allow manufacturers to install drivers without putting them into the Android kernel source (which apparently voids them the responsibility of publishing source codes) however .so's are NOT inter-compatible with different systems, IE bada .so files will likely fail if you attempt to use them on Linux kernel and vice versa, even Linux .so's for a slightly different Linux kernel version fail to load.(".ko" files are Linux kernel modules, ".so" files have been described as some form of software/native code libraries)
as for storage space on the "ext2system.img" file, it is generally mounted as read-only by the system and not modified unless your modding, the space in ext2system.img is normally not used for install of applications or for file/document/save storage of any kind.
sorry if this post doesn't make much sense, I in fact know very little about the inner workings of android, I mainly contributed slightly to modifications on init.rc:
http://code.google.com/p/badadroid/source/browse/trunk/nbates_files/xxjpxinitramloop030711/init.rc
EDIT: regarding the QMG format I just had a rethink and remembered that the Galaxy i9000 (from which this firmware came from) has a completely different modem configuration other than manufacturer (Qualcomm) yet the animation plays fine on Wave S8500, so possibly not the modem that is processing it in this case.
EDIT2: wrong about ".so" files
Hello guys, please make me clear this. I own a samsung wave y s5380 with bada 2,0 os the phone has a 832 mhz cpu, can this phone support Android?Can I upgrade os to android instead of bada?Please answer me I searched whole internet and didn't find any tread or post to say something about if this can be done or not.Thank you and have a good day.
Hello guys, please make me clear this. I own a samsung wave y s5380 with bada 2,0 os the phone has a 832 mhz cpu, can this phone support Android?
Click to expand...
Click to collapse
S5620...
http://darkforestgroup.com/forum/index.php/topic,9231.0.html
This is Broadcom based...
...I searched whole internet...
Click to expand...
Click to collapse
Sure...
This is the reason why you think its easy to port to every device...
Your handset S5380 is also Broadcom based...
BUT this all on similarity with S5620 Monte....
S5380 NO known or confirmed Android solution yet...
Sorry.
If wrong answer.
Sorry.
Best Regards
I still hope that will appear something that can I upgrade from bada to android (
I still hope that will appear something that can I upgrade from bada to android...
Click to expand...
Click to collapse
Hope ever dies at last...
BUT why the hell you buy an bada handset, if you love Android?
Fastest working solution for your problem is.
Buy Android handset.
If you have time... much time.
Range between 0 and open end... (in years)
Then wait or maybe port self Android to your handset.
No joke...
There are several projects to port Android to unsupported handsets...
Why not start new project for S5380...
You need only NEW Devs... so you can recruit NEW Team members.
It makes sense ... user with S5380 or Broadcom knowledge like Monte team...
Again. For Broadcom I know only this:
http://darkforestgroup.com/forum/index.php/topic,9231.0.html
Good luck.
Best Regards
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 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.