Database Info

[CM RECOVERY] Sources released, Private alpha testing stage

Hi All!
I pushed my fork back to GITHUB
I compiled CM recovery for Galaxy 3, it was long journey
I need some help. My development speed is very low, I'm not dev at all and my C knowledge is very limited. Also I can't invest many time in porting CM recovery.
Thing that worked for my setup (/system - rfs /data ext2 /cache - ext2):
1. it compiled!
2. partitioning SD card
3. making backup
4. restoring data partition (other parts and boot/recovery not tested)
5. wipe cache paritions
6. running fix_permissions scripts
7. running keypress test
I want You to help me choose that to do next: make update.zip worked or try to do backup/restore fully working?
Also I need link for update.zip that surely worked for JPM to test it.
recovery is in pre-alpha stage, I don't want do public alphas, because it simply not tested, and really may brick phones
Now recovery in private alpha testing stage, PM me if you brave, want to test alpha and accept risk of bricking you device

good job.
I don"t know if I can help you much but I will try if you need to.

FS supported by builds:
Build # /system /data /cache
26 rfs ext2 ext2
27 ext2 ext2 ext2
30 ext2 ext4 ext2

Good job
You can give it to some testers though willing to test even at the risk of bricking so that devs like you are motivated and get feedback
Testing really helps
I can help too

if you are porting cwm recovery latest version it uses newer scripting language and thus old update.zip files wont work anyway.

finally! SG3 is becoming a good phone lol ! thanks!

subscribed...
i´d suggest to make nandroid backup work first, then the danger of having a softbrick is much smaller.

That's fantastic news !
Backup/recovery should be top priority I think. Flashing update.zip is not something we could do before, so we won't miss that.

Bubble-be said:
That's fantastic news !
Backup/recovery should be top priority I think. Flashing update.zip is not something we could do before, so we won't miss that.
Click to expand...
Click to collapse
we could do it with eclair...

FadeFx said:
if you are porting cwm recovery latest version it uses newer scripting language and thus old update.zip files wont work anyway.
Click to expand...
Click to collapse
My developing speed is really slow, I start porting it ~1.5 months ago
Version is ClockworkMod Recovery v2.5.1.8 is it old or new version for update.zip ?

making everything to work would be awesome... i believe in you ppl! you will make it work! you have to make it work! because no one else is even close to being capable of doing the magic that you are doing!

the new script version is out for 3 or month or 4 so already...

Nice work
Do you know when you release the 1st beta?

its done when its done... dont ask dont tell...

deskjeti said:
Nice work
Do you know when you release the 1st beta?
Click to expand...
Click to collapse
dude read>
recovery is in pre-alpha stage, I don't want do public alphas, because it simply not tested, and really may brick phones

mumbozver said:
Hi All!
I compiled CM recovery for Galaxy 3, it was long journey
Click to expand...
Click to collapse
Maybe the best news concerning the g3 in a long time. Keep it up man! I am not able to do much but I'm eager to beta test!
sent from my kirillos' v.3 fugumod 2.2 BE oc'd JIT enabled nokia 3210

can you gine me workin fix_permissions scripts to use it from internal use ?> thanks in advance

You can test the recovery by using terminal.But there's a problem that u can't return to normal system.I think it 's because the video driver return to basic mode etc.(Just guess it)I sugggest u don't compile all parts of the cwm but a little part.For we just need a little function now.Test it in terminal.While I have a computer.I will try to help,but I can't promise anything...Haha
Sent from my GT-I5800 using XDA Premium App
WHEN I USING ENGLISH IN COMUNNICATING WITH OTHERS. SOMEONE WILL TELL ME:U CAN PASS THE CET-4 EASILY....

nikkpap said:
can you gine me workin fix_permissions scripts to use it from internal use ?> thanks in advance
Click to expand...
Click to collapse
"worked" mean it runs fine from recovery menu, and do its job.
It's unmodified, and I'm not sure it fully correct for our phone.
You may find it here: https://github.com/CyanogenMod/android_bootable_recovery/blob/froyo-stable/utilities/fix_permissions

instead of making update.zip work, u can complete the nandroid and backup\restore
i flashed cm7 in my friend's X8
the update.zip did not work properly so i extracted the rom files and made them as a backup and restored the rom with that backup-worked like a charm
we can install roms if the dev's provided it as a backup file(which is safer than using update.zip)

[DEV]porting b2g

small update again:
I could write down my steps so a real developer could take over
Here my errors so far:
Symlinks for x/opengl-libs not right (ubuntu 12 error, had to do this manually)
Wifi-driver not found (Taken out of BoardConfig.mk)
Camera cpp-files contain some errors (No time to solve these, taken out of BoardConfig.mk)
Fonts not found (I simply copied those to the destination they should be created - works)
Kernel cant be build. No solution so far.
Again, this is basically ICS, nothing special. Except you dont need dalvik and stuff. Instead you need a ICS-kernel with a slightly different init.rc (containing the b2g layer).
The basic steps are shown here:
https://wiki.mozilla.org/B2G/Porting
Code:
Finding NOTICE files: out/target/product/ariesve/obj/NOTICE_FILES/hash-timestamp
Combining NOTICE files: out/target/product/ariesve/obj/NOTICE.html
Installed file list: out/target/product/ariesve/installed-files.txt
Target system fs image: out/target/product/ariesve/obj/PACKAGING/systemimage_intermediates/system.img
in mkuserimg.sh PATH=out/host/linux-x86/bin/:/home/max/dev/B2G/build/fake-jdk-tools/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/max/dev/B2G/out/host/linux-x86/bin:/home/max/dev/B2G/prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin:/home/max/dev/B2G/development/emulator/qtools:/home/max/dev/B2G/prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin:/home/max/dev/B2G/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
make_ext4fs -s -l 545259520 -a system out/target/product/ariesve/obj/PACKAGING/systemimage_intermediates/system.img out/target/product/ariesve/system
Creating filesystem with parameters:
Size: 545259520
Block size: 4096
Blocks per group: 32768
Inodes per group: 6656
Inode size: 256
Journal blocks: 2080
Label:
Blocks: 133120
Block groups: 5
Reserved block group size: 39
Created filesystem with 536/33280 inodes and 19176/133120 blocks
make: *** Keine Regel vorhanden, um das Target »out/target/product/ariesve/kernel«,
benötigt von »out/target/product/ariesve/boot.img«, zu erstellen. Schluss.
yeah... ubuntu automatically uses German here
The BoardConfig.mk points to
Code:
TARGET_PREBUILT_KERNEL := device/samsung/ariesve/prebuilt/zImage
What I tried:
I simply renamed my repacked kernel with the changed init.rc to "kernel". Its building then, but heimdall doesnt accept my kernel
The https://wiki.mozilla.org/B2G/Porting porting guide doesnt explain this very well :S Ill keep on digging through the makefiles
Im sorry I didnt manage to get it booting but its my first experience in rom developing so Im not into ICS development which would be a great help I think

I could upload all the files I have so far in case somebody is interested.

Noob here. What the f*** is B2G?

Gusta_HR said:
Noob here. What the f*** is B2G?
Click to expand...
Click to collapse
Google is your best friend; Boot to Gecko. Mozilla's open source linux based mobile OS, mainly working with apps and stuff written in html5, effectively making the entire os some sort of browser.
I'm not sure though if it is possible to build b2g on anything apart from the devices listed on this page https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Building_B2G_for_Samsung_Galaxy_S2
Sent from my GT-I9001 using xda app-developers app

http://www.youtube.com/watch?v=lHKNt0n6whw
Ive seen it on a friends s2 and I would like to see it working on my i9001 so I try porting on my own.

wietwiet said:
Google is your best friend; Boot to Gecko. Mozilla's open source linux based mobile OS, mainly working with apps and stuff written in html5, effectively making the entire os some sort of browser.
I'm not sure though if it is possible to build b2g on anything apart from the devices listed on this page https://developer.mozilla.org/en/Mozilla/Boot_to_Gecko/Building_B2G_for_Samsung_Galaxy_S2
Click to expand...
Click to collapse
There was a porting thread in the b2g developers forum which was turned into a wiki page here

Oh i see..another worthless port
sent from the other side of my Galaxy

Gusta_HR said:
Oh i see..another worthless port
sent from the other side of my Galaxy
Click to expand...
Click to collapse
why should it be worthless?
i would like to have gecko on my s plus

Gusta_HR said:
Oh i see..another worthless port
Click to expand...
Click to collapse
Maybe to most, but I would like to try.

Gusta_HR said:
Oh i see..another worthless port
sent from the other side of my Galaxy
Click to expand...
Click to collapse
Whats your problem? If you dont want to use it then just ignore this Thread but please dont spam it with your pessimistic Comments

Sot0 said:
Whats your problem? If you dont want to use it then just ignore this Thread but please dont spam it with your pessimistic Comments
Click to expand...
Click to collapse
I was allways looking info about B2G when i first find out about it.
Please port it, it would be great! I always wanted a "mozilla" phone xD

+1
I'll also try to port when I'll finish my holidays!!!

sapsa said:
I was allways looking info about B2G when i first find out about it.
Please port it, it would be great! I always wanted a "mozilla" phone xD
Click to expand...
Click to collapse
I am basically done. The guide is easy to follow. Most of the work is already done by arco.
But I dont want to risk bricking my phone as I need it for my exams next week
So I just want a developer to roughly check things and inform me about any riscs.

It seems as you just need a working ICS rom kernel. You just add a few b2g things and in the b2g files you have to point to a few phone specific files (drivers etc). Then you just need to change the scripts thatll flash the resulting "rom", which should be easy as we can use heimdall just like s2 which should/can be used as a references for new devices as described in the wiki.
For heimdall see:
http://forum.xda-developers.com/showthread.php?t=755265
I just dont see a point in making a git repo for this as I only changed a couple of files so I wanted to describe the process making it easy for a developer to see what I made.

sc4les said:
I am basically done. The guide is easy to follow. Most of the work is already done by arco.
But I dont want to risk bricking my phone as I need it for my exams next week
So I just want a developer to roughly check things and inform me about any riscs.
Click to expand...
Click to collapse
Well, upload what you got. Does it come as a cwm flashable file, or a file that needs to be flashed in odin? If it's a cwm flashable, it should be easy to check if the updater script is correct. A cwm flashable shouldn't cause any damage if b2g isn't working, since you can simply restore a backup.
Sent from my GT-I9001 using xda app-developers app

It contains a shell script that uses heimdall, which uses the odin protocol.

Glad to see something new being developed here. ^_^
About risks of bricking the device..perhaps this can help you understand better..its more related to partitions and so on:
>> http://forum.xda-developers.com/wiki/Samsung_Galaxy_S_Plus/GT-I9001#Partitions
I've seen a video about B2G ported to SGS2..according to the preview, it seems a sluggish and has a very terrible response (processing speed).
Perhaps if this works, maybe you can try porting Ubuntu OS itself to i9001 (in the future).

Hey guys im back from france! ive made a test build before i went to france. But it didnt boot. i will post it tonight tho!

broodplank1337 said:
Hey guys im back from france! ive made a test build before i went to france. But it didnt boot. i will post it tonight tho!
Click to expand...
Click to collapse
Could you post/message me how you did it? I'm curious

So I started from scratch to check everything twice.
Here are my files so far:
http://dl.dropbox.com/u/22946117/b2g.zip
Things that must be done:
Clone B2G repo [x]
Create local backup of the original Android system [ ]
Add new device in config.sh [x]
Create manifest file "default.xml" for new device [x]
{not sure where to put it so its in /b2g/default.xml}
Create configuration tree for new device [x]
{is in /b2g/device/samsung/galaxysplus/}
The need to rebuild boot.img [ ]
{boot.img is in /b2g/device/samsung/galaxysplus/boot.img and MANIFEST, not sure where to put these. I made no changes yet, though this is pretty easy}
Add new device in flash.sh [?]
{should be the same as for gs2}
Config/build/flash for new device [ ]
{should work soon, gonna replace my arch with ubuntu for this}
anyone interested in making a git repo?

[DEV] MSM7x30 Open Source Bootloader '(L)ittle (K)ernel'

Hey guys,
while searching around the web I saw this very interesting and hot topic on CAF.
https://www.codeaurora.org/2010/03/02/little-kernel-based-android-bootloader/
Sources:
https://github.com/travisg/lk/commits/master
fixes for 7x30:
https://android.googlesource.com/kernel/lk/+/qcom-dima-7x30-fixes/AndroidBoot.mk
Simlar projects:
http://forum.xda-developers.com/showthread.php?t=2147997
http://rtammekivi.tumblr.com/post/18995217696/working-little-kernel
http://www.pocketpc.ch/htc-hd2-andr...smiths-little-kernel-loader-installation.html
The thing is, I'm not that good to compile it for our device.
I hope someone more advanced than me is able to compile that without hardbricking his phone...
Regards
trapjul

AW: [DEV] MSM7x30 Open Source Bootloader '(L)ittle (K)ernel'
This looks very interesting. But i dont know why you think this will get us dualboot?
But i would really love to.have fastboot. Its very handy and easy to use.
Sent from my GT-I9001 using xda app-developers app

XeLLaR* said:
This looks very interesting. But i dont know why you think this will get us dualboot?
But i would really love to.have fastboot. Its very handy and easy to use.
Sent from my GT-I9001 using xda app-developers app
Click to expand...
Click to collapse
Because the current problem at Dual Boot is the switch between the kernels. With an Open Source Bootloader we could switch between them mich more easy.

trapjul said:
Because the current problem at Dual Boot is the switch between the kernels. With an Open Source Bootloader we could switch between them mich more easy.
Click to expand...
Click to collapse
Dual boot needs some where for storing second rom 's data / cache / & most important thing is BattertState which can cause lots of problem in dual ROM mod !
Another thing :: we have secondary boot loader which made our device harder to brick so do not worry about ! Your device just breaks when you wipe both boots !

Dead thread ? I think LK is a good project !?!

I think this is a good start!
But I'm sorry, I have too less knowledge of Linux/Android :/
I can't help you...
Maybe I can test it
(of course when there is no risk that I break my phone )

I think it's difficult to make it for our device full working, that's the problem.

Harrocan said:
I think it's difficult to make it for our device full working, that's the problem.
Click to expand...
Click to collapse
No !
You need to just make up it for MSM7X30 , boot loader loads up by SoC then loads Boot.img ! It won't need any GPU driver or WiFi driver or can driver ! Just you need to port it to msm7x30 which the LK progect supports it !

I've tried to compile it several times but I couldn't make it work for our board so far.
Also how in earth will we implement this into our system ?
Anyways I think this is a great project. I would love to make a custom bootloader if the information is there.

AW: [DEV] MSM7x30 Open Source Bootloader '(L)ittle (K)ernel'
Maybe a look here is helpful: https://github.com/chirayudesai/android_bootable_bootloader_lk
Sent from my GT-I9100 using xda app-developers app

Isn't it what we need? https://www.codeaurora.org/cgit/ext...sm7630_surf/tree/AndroidBoard.mk?h=jb_2.1.3.7
Tapatalk 4 küldve GT-I9001-ről

czobor said:
Isn't it what we need? https://www.codeaurora.org/cgit/ext...sm7630_surf/tree/AndroidBoard.mk?h=jb_2.1.3.7
Tapatalk 4 küldve GT-I9001-ről
Click to expand...
Click to collapse
what i see the problem in:
your suggestion is for msm7630.
we have/need msm7x30.

Lei M said:
what i see the problem in:
your suggestion is for msm7630.
we have/need msm7x30.
Click to expand...
Click to collapse
That's the same.
Tapatalk 4 küldve GT-I9001-ről

czobor said:
That's the same.
Click to expand...
Click to collapse
do you have a source for your information?
it's very strange:
according to http://en.wikipedia.org/wiki/MSM7000 it could be the same but if you take a look here: http://en.m.wikipedia.org/wiki/Snapdragon_(system_on_chip) you see that the msm7630 only has 800MHz cpu
edit:
http://snapvoip.blogspot.co.at/2009/11/qualcomm-introduces-new-mobile-msm7x30.html?m=1
says that msm7x30 is a family of chipsets.

Before doing any thing we have to establish a UART or JTAG Connection to board

I am a total noob at this, but:
My opinion is that if we can access and modify or divide /system /data and /cache on out like, it would be easy to install 2 ROMs.
For example system is mmcblk08
Divide it in 08 and 09.We have 2x /system.Do this with /data, /cache /ramdisk.
But booting is a prob here.
I may be wrong.I don't know if we can touch those partitions.

Costinutz32 said:
I am a total noob at this, but:
My opinion is that if we can access and modify or divide /system /data and /cache on out like, it would be easy to install 2 ROMs.
For example system is mmcblk08
Divide it in 08 and 09.We have 2x /system.Do this with /data, /cache /ramdisk.
But booting is a prob here.
I may be wrong.I don't know if we can touch those partitions.
Click to expand...
Click to collapse
No. We cannot do that. mmcblk0p9 is the ADSP partition (it deals with encoding and decoding video and things like this). And, we cannot modify the bootloaders either, that would require a direct hardware connection through UART. This CAF project is really not that useful for our device...
What we can do for dual-booting is simply partition the ext-sd like we did with the /data on bricked emmc devices, but I'm not sure the system can be mounted on it....
Anyways, managing two backups of two different ROM's can give the same result, but it takes more time.

educk said:
No. We cannot do that. mmcblk0p9 is the ADSP partition (it deals with encoding and decoding video and things like this). And, we cannot modify the bootloaders either, that would require a direct hardware connection through UART. This CAF project is really not that useful for our device...
What we can do for dual-booting is simply partition the ext-sd like we did with the /data on bricked emmc devices, but I'm not sure the system can be mounted on it....
Anyways, managing two backups of two different ROM's can give the same result, but it takes more time.
Click to expand...
Click to collapse
This was just an example, i didn't even know it mmcblk09 exists.

educk said:
And, we cannot modify the bootloaders either, that would require a direct hardware connection through UART. This CAF project is really not that useful for our device...
Click to expand...
Click to collapse
As far as I know the Xperia T hasnt UART too. Wherefor do you need UART? I would just override the bootloader partitions via command line because in a running system the bootloader shouldnt be mounted or even used.
At all it shouldnt be toooo impossible because it has intial support for 7x30...
trapjul

trapjul said:
As far as I know the Xperia T hasnt UART too. Wherefor do you need UART? I would just override the bootloader partitions via command line because in a running system the bootloader shouldnt be mounted or even used.
At all it shouldnt be toooo impossible because it has intial support for 7x30...
trapjul
Click to expand...
Click to collapse
How can you debug a bootldr if no UART is given? The first compiled LK-bootldr will 100% not work correctly, which means the phone will NOT work at all after that! Then you need a UART connection, to revert to the old bootloader or to debug through UART. The Final WORKING build can be flashed through terminal, but the developer who has to get through all the debugging must have UART.
UART

[i9103][CWM Advanced Edition] PhilZ Touch

Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Special thanks to @Adam77Root for his work to make this possible
Download links
Last version can be found here:
i9103
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
http://d-h.st/users/philz_touch/?fld_id=18564#files
Click to expand...
Click to collapse

Great to see Philz at R forum. First Adam's Official Cm10.1 then Official PAC now Official Support of Philz recovery.:good:
Edit: status 0 error occurs when i flash using cwm.

Disturbed™ said:
Edit: status 0 error occurs when i flash using cwm.
Click to expand...
Click to collapse
Replace the update-binary with this.
Sent from my GT-I9103

Adam77Root said:
Replace the update-binary with this.
Sent from my GT-I9103
Click to expand...
Click to collapse
Sorry,
Missed this from your feedback PM
Just fixed the zip on download server
Now, it should flash correctly
Many thanks for the support :good:

Finally Flash it (Thanks Adam)
Working Great.
1) Touch is working great. - It will work after 5-6 Seconds.(If possible just press back Hardware key)
2) Its Superfast.
3) Approx 90% functions are working.(A normal day user can flash it without any problem.
4) Taking backing up normally & deleting data & caches also.
Few bugs:
1) you can't view what you are flashing ( Texts are going quickly downwards to front page & hence you can't see it)
2) 1 or 2 functions aren't working(might be my R problem).
I m attaching the zip file with Adam's Update - binaries.
Flash it & Enjoy. :good:

Disturbed™ said:
Finally Flash it (Thanks Adam)
Working Great.
1) Touch is working great. - It will work after 5-6 Seconds.(If possible just press back Hardware key)
2) Its Superfast.
3) Approx 90% functions are working.(A normal day user can flash it without any problem.
4) Taking backing up normally & deleting data & caches also.
Few bugs:
1) you can't view what you are flashing ( Texts are going quickly downwards to front page & hence you can't see it)
2) 1 or 2 functions aren't working(might be my R problem).
I m attaching the zip file with Adam's Update - binaries.
Flash it & Enjoy. :good:
Click to expand...
Click to collapse
- About text going too fast: try to enable both "Easy Log View" and "Pause on Logs" options. This should fix it. In a future version, ui_print text will have its own row height, not shared with menu height
- About non working functions: provide a description + log (Advanced / Report Error and attach file here)

Phil3759 said:
- About text going too fast: try to enable both "Easy Log View" and "Pause on Logs" options. This should fix it. In a future version, ui_print text will have its own row height, not shared with menu height
- About non working functions: provide a description + log (Advanced / Report Error and attach file here)
Click to expand...
Click to collapse
Thanks for the quick response buddy. I will provide you the same. But its time for my B'day party.:laugh:

run's on stock ics?
Is a awesome recovery y test in s2

Sesme said:
run's on stock ics?
Is a awesome recovery y test in s2
Click to expand...
Click to collapse
Didn't get you buddy, come again.?

Sesme said:
run's on stock ics?
Is a awesome recovery y test in s2
Click to expand...
Click to collapse
This recovery is particularly for the galaxy r. Do not flash it on the s2
Sent from my GT-I9300

pulley06 said:
This recovery is particularly for the galaxy r. Do not flash it on the s2
Sent from my GT-I9300
Click to expand...
Click to collapse
no run's on stock ics no format no flash rom's...return to CWM 5

will this file works on n7100 to?
Disturbed™ said:
Finally Flash it (Thanks Adam)
Working Great.
1) Touch is working great. - It will work after 5-6 Seconds.(If possible just press back Hardware key)
2) Its Superfast.
3) Approx 90% functions are working.(A normal day user can flash it without any problem.
4) Taking backing up normally & deleting data & caches also.
Few bugs:
1) you can't view what you are flashing ( Texts are going quickly downwards to front page & hence you can't see it)
2) 1 or 2 functions aren't working(might be my R problem).
I m attaching the zip file with Adam's Update - binaries.
Flash it & Enjoy. :good:
Click to expand...
Click to collapse
do you know if this file works on n7100 to?

xastunts said:
do you know if this file works on n7100 to?
Click to expand...
Click to collapse
No buddy.

xastunts said:
do you know if this file works on n7100 to?
Click to expand...
Click to collapse
But n7100 version exists since months now...
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
But n7100 version exists since months now...
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
yes but we have previous version philz_touch_5.06.1-n7100.zip
they got the philz_touch_5.07 which i believe has exfat support for ext sd and thats why i wanted it

xastunts said:
yes but we have previous version philz_touch_5.06.1-n7100.zip
they got the philz_touch_5.07 which i believe has exfat support for ext sd and thats why i wanted it
Click to expand...
Click to collapse
Please read change log carefully. If there were really needed things, i'd have updated. Exfat works on n7100 since first release, months ago.
Last version has even a bug in custom restore that no one even noted (it doesn't affect integrity and nandroid function by the way)
Sent from my GT-I9100 using Tapatalk 2

Phil3759 said:
Please read change log carefully. If there were really needed things, i'd have updated. Exfat works on n7100 since first release, months ago.
Last version has even a bug in custom restore that no one even noted (it doesn't affect integrity and nandroid function by the way)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
AAh damn it! i apologize! i mixed this up with the devil dual boot recovery! that one didnt have exfat support so i needed to mount another ext sd card in fat32 and swap it when i was in other roms. pretty annoying!
no ur right urs works! i know cause my exfat is inserted and booting through ur recovery all day long trying to find my soul mate os lol.
thx alot for the stuff you do for us! ur our hero!

is there a 100% full format option in ur recovery?
Phil3759 said:
Please read change log carefully. If there were really needed things, i'd have updated. Exfat works on n7100 since first release, months ago. http://icons.media.xda-developers.com/images/editor/separator.gif
Last version has even a bug in custom restore that no one even noted (it doesn't affect integrity and nandroid function by the way)
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
dr phil! i got you a question ! . is there a 100% full format option availible in ur recovery? if it is please state where.
even after using clean to install new rom i can see alot of junk files on my phones folders when connected to the pc. some photos from viber and alot of empty folders from apps i have uninstalled months ago.
is there no way to make a real clean whipe and have nothing at all left except important os file tree?
thx for reply! i try to pay you back in a good favour

xastunts said:
dr phil! i got you a question ! . is there a 100% full format option availible in ur recovery? if it is please state where.
even after using clean to install new rom i can see alot of junk files on my phones folders when connected to the pc. some photos from viber and alot of empty folders from apps i have uninstalled months ago.
is there no way to make a real clean whipe and have nothing at all left except important os file tree?
thx for reply! i try to pay you back in a good favour
Click to expand...
Click to collapse
remaining files are sdcard contents. YOu can remove by formatting sdcard. That won't be done automatically to avoid people loosing their data

Phil3759 said:
remaining files are sdcard contents. YOu can remove by formatting sdcard. That won't be done automatically to avoid people loosing their data
Click to expand...
Click to collapse
thx alot for reply! deeply appreciate it!:angel: how about using ur aroma browser that is built in inside the recovery and mark all files and just delete them ? will i be able to reboot into recovery mode after that? i was thinking that recovery files where flashed into a flash memory outside the phones internal memory to be a fail safe place harmless for beeing erased unless flashed with odin or flashed with any compatible recovery we got availible. am i right about this?
so my short question again is can i mark all folders and files and delete them directly through the built in aroma browser?
:good:
im willing to write you good comments and review here or on youtube if it is in ur demands.

[Q] Flashing different system img.

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

SEXCrow said:
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
Click to expand...
Click to collapse
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:laugh:

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

SxCrow said:
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
Click to expand...
Click to collapse
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:laugh:

M_Maha said:
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:laugh:
Click to expand...
Click to collapse
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

SxCrow said:
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
Click to expand...
Click to collapse
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/showthread.php?t=2319018
http://forum.xda-developers.com/showthread.php?t=1971915
http://forum.xda-developers.com/showthread.php?t=1659584
http://forum.xda-developers.com/showthread.php?t=1630130
http://forum.xda-developers.com/showthread.php?t=633246

Thanks But....
M_Maha said:
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/showthread.php?t=2319018
http://forum.xda-developers.com/showthread.php?t=1971915
http://forum.xda-developers.com/showthread.php?t=1659584
http://forum.xda-developers.com/showthread.php?t=1630130
http://forum.xda-developers.com/showthread.php?t=633246
Click to expand...
Click to collapse
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

SxCrow said:
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
Click to expand...
Click to collapse
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:laugh: