LG G3 Receives Oversharpening Fix via Modified Kernel

Nothing is perfect, as they say. No matter how alluring or seemingly perfect, … more

APKTool Updated with Android Lollipop Support

One of the beauties of Android is the level of flexibility we have over our devices. Whether … more

Lollipop Leak for Sprint Galaxy S5, TWRP for Micromax Canvas Magnus – XDA TV

Android 5.0 Lollipop has been leaked for the Sprint … more

Velocity is Like OpenTable on Steroids

We all enjoy a night out with friends or our significant other from time to time. However, there is … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[Q] Flashing different system img.

OP SxCrow

1st June 2014, 08:29 AM   |  #1  
SxCrow's Avatar
OP Junior Member
Flag Ghaziabad
Thanks Meter: 0
 
5 posts
Join Date:Joined: Apr 2014
More
Hello friends ....
This is my first querry to the forum Iam a kind of new to the ways of... how the things work when you flash images.....so this is how it goes..

I Have MicromaxA65 it has a
System rom capacity of 222mb...out of which 173.6mb is allocated and 48.4 mb is vacant .
It has a separate internal storage of 176mb
I have system img of Micromax A67 orA68 which is Ics and my current default Rom is gingerbread....
I was wondering if i could flash
A66 or A67 system.img over my A65 sys.img
The size of A66 or A68 Stock image size is 185MB and 218mb ...

1-Do you guys thinks it is possible...or is it noob to ask??


2-CAN anyone also tell me where are the driver loading file located ...are they on Boot.img or Sys.img.
Considering they may increase my chances of bricking...?

3-CAN any one tell me whether the System.img size increase or decrease during flashing.. or it remains the same...?


4- CAN anyone tell me whether the system memory space only used for sys.img flasing or
..boot.img and other things are also present in it...?


6-WHATS ARE THE CHANCES OF BRICKING ....?

7- Last and least Can anyone tell me a software to effeciently open those .img files?

All the refrence of the system memory space I have made.... are linked to the one shown by the Titanium Backup Application.....

Can any explain me whole concept..?


Thanks to all

Cheers..

Sent from my Micromax A65 using XDA Free mobile app



Sent from my Micromax A65 using XDA Free mobile app
1st June 2014, 12:33 PM   |  #2  
Member
Thanks Meter: 14
 
54 posts
Join Date:Joined: May 2014
Info 2
Quote:
Originally Posted by SEXCrow

Hello friends ....
This is my first querry to the forum Iam a kind of new to the ways of... how the things work when you flash images.....so this is how it goes..

I Have MicromaxA65 it has a
System rom capacity of 222mb...out of which 173.6mb is allocated and 48.4 mb is vacant .
It has a separate internal storage of 176mb
I have system img of Micromax A67 orA68 which is Ics and my current default Rom is gingerbread....
I was wondering if i could flash
A66 or A67 system.img over my A65 sys.img
The size of A66 or A68 Stock image size is 185MB and 218mb ...

1-Do you guys thinks it is possible...or is it noob to ask??


2-CAN anyone also tell me where are the driver loading file located ...are they on Boot.img or Sys.img.
Considering they may increase my chances of bricking...?

3-CAN any one tell me whether the System.img size increase or decrease during flashing.. or it remains the same...?


4- CAN anyone tell me whether the system memory space only used for sys.img flasing or
..boot.img and other things are also present in it...?


6-WHATS ARE THE CHANCES OF BRICKING ....?

7- Last and least Can anyone tell me a software to effeciently open those .img files?

All the refrence of the system memory space I have made.... are linked to the one shown by the Titanium Backup Application.....

Can any explain me whole concept..?


Thanks to all

Cheers..

Sent from my Micromax A65 using XDA Free mobile app



Sent from my Micromax A65 using XDA Free mobile app



Frankly, you cannot flash a rom for different device cause the kernel would be different. There would be a high chance of bricking is 100 % if you flash another phones rom


However if the kernels are matching then you may flash the rom . { though I suggest not coz the phones are different and kernels are rarely totally same } you may encounter some bugs because of that . Like some feature of your phone not working coz it isnt present in the other phone


But you may flash roms meant for your phone safely ( I'm not discouraging you from romming and theming )


HIT THANX IF I HELPED
1st June 2014, 04:59 PM   |  #3  
SxCrow's Avatar
OP Junior Member
Flag Ghaziabad
Thanks Meter: 0
 
5 posts
Join Date:Joined: Apr 2014
More
Can anyone explain me the concept behind the system space ......what does that 222 mb means ....

I will check for the kernel version....
Have to extract the images first from the stock ROM:banghead:

Is kernel version on boot image ?
Well If i do a flash with different system ROM will my usb dribers load....Please answer my query any one by one.....I will be thankful...

Sent from my Micromax A65 using XDA Free mobile app
1st June 2014, 07:26 PM   |  #4  
Member
Thanks Meter: 14
 
54 posts
Join Date:Joined: May 2014
Quote:
Originally Posted by SxCrow

Can anyone explain me the concept behind the system space ......what does that 222 mb means ....

I will check for the kernel version....
Have to extract the images first from the stock ROM:banghead:

Is kernel version on boot image ?
Well If i do a flash with different system ROM will my usb dribers load....Please answer my query any one by one.....I will be thankful...

Sent from my Micromax A65 using XDA Free mobile app

The 222 mb is the system memory chip called EMMC or NAND memory hence the rom backups are also called Nandroid backups
It houses your OS and you should perform a backup before you flash other ROMS

Whether your usb drivers will load after you flash a ROM meant for other phones is unpredictable, they may work or they may not ( My guess is they will work , but cant be sure about it)


HIT THANX IF I HELPED YOU
2nd June 2014, 05:40 AM   |  #5  
SxCrow's Avatar
OP Junior Member
Flag Ghaziabad
Thanks Meter: 0
 
5 posts
Join Date:Joined: Apr 2014
More
Quote:
Originally Posted by M_Maha

The 222 mb is the system memory chip called EMMC or NAND memory hence the rom backups are also called Nandroid backups
It houses your OS and you should perform a backup before you flash other ROMS

Whether your usb drivers will load after you flash a ROM meant for other phones is unpredictable, they may work or they may not ( My guess is they will work , but cant be sure about it)


HIT THANX IF I HELPED YOU

Thanx for the I know that it is NAND FLASH MEMORY ..
Can be flashed easily....
My question was whether the partion on which sys.img is flashed is different or it the same as of boot.img....?

Whether the size of the image increase during a flash..?

Can you name me a software on which i can open
Img files .....?


I will go ahead and check the kernel version...


Sent from my Micromax A65 using XDA Free mobile app
2nd June 2014, 08:04 AM   |  #6  
Member
Thanks Meter: 14
 
54 posts
Join Date:Joined: May 2014
Quote:
Originally Posted by SxCrow

Thanx for the I know that it is NAND FLASH MEMORY ..
Can be flashed easily....
My question was whether the partion on which sys.img is flashed is different or it the same as of boot.img....?

Whether the size of the image increase during a flash..?

Can you name me a software on which i can open
Img files .....?


I will go ahead and check the kernel version...


Sent from my Micromax A65 using XDA Free mobile app

Now there are many tools to unpack and repack boot.img and kernel
I will give you the links you will have to select which one fulfills your purposes and which is easy to use for you

http://forum.xda-developers.com/show....php?t=2319018

http://forum.xda-developers.com/show....php?t=1971915

http://forum.xda-developers.com/show....php?t=1659584

http://forum.xda-developers.com/show....php?t=1630130

http://forum.xda-developers.com/showthread.php?t=633246
The Following User Says Thank You to M_Maha For This Useful Post: [ View ]
13th June 2014, 09:58 AM   |  #7  
SxCrow's Avatar
OP Junior Member
Flag Ghaziabad
Thanks Meter: 0
 
5 posts
Join Date:Joined: Apr 2014
More
Thanks But....
Quote:
Originally Posted by M_Maha

Now there are many tools to unpack and repack boot.img and kernel
I will give you the links you will have to select which one fulfills your purposes and which is easy to use for you

http://forum.xda-developers.com/show....php?t=2319018

http://forum.xda-developers.com/show....php?t=1971915

http://forum.xda-developers.com/show....php?t=1659584

http://forum.xda-developers.com/show....php?t=1630130

http://forum.xda-developers.com/showthread.php?t=633246


The kernel is present in the BOOT.img for the stock ROMS
and zImage for custom ROMs ...
to change the kernel i can flash different boot.img
there are various kernels on this site
but my boot partion is very less
Is there any way i can redistribute the partition ...?
I will have to use cygwin to open the boot.img
and to deal with other stuff though its slow
I have check the kernel coding
but theres a lot of problems
First the coding for ARM processor is diferent than the usual IA-x86 and 64 bit processors
NASM and lebmo re of no use...

I really need someone to work with me
someone experience
13th June 2014, 05:50 PM   |  #8  
Member
Thanks Meter: 14
 
54 posts
Join Date:Joined: May 2014
Post
Quote:
Originally Posted by SxCrow

The kernel is present in the BOOT.img for the stock ROMS
and zImage for custom ROMs ...
to change the kernel i can flash different boot.img
there are various kernels on this site
but my boot partion is very less
Is there any way i can redistribute the partition ...?
I will have to use cygwin to open the boot.img
and to deal with other stuff though its slow
I have check the kernel coding
but theres a lot of problems
First the coding for ARM processor is diferent than the usual IA-x86 and 64 bit processors
NASM and lebmo re of no use...

I really need someone to work with me
someone experience

Dont use any kernels not meant for your device. If the boot.img is bigger than your partition then it definitely isnt made for your device. You can port kernels of other devices.

Are you trying to make or port a new kernel??

Anyways I can't help you, I havent got the time or the phone!!

However you can try the Micromax A65 forums for some help

And you can always contact me

HIT THANX IF I HELPED YOU
Last edited by M_Maha; 13th June 2014 at 05:55 PM.

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes