Related
HOW TO ROOT YOUR MICROMAX A58
1. go to settings-> Security-> enable Unknown sources.
2. go to about phone in in settings -> About phone -> tap on the build number several times to enable developer options
3. in settings-> Developer options -> enable Usb Debugging
4. Now download framaroot 1.8.1 apk. download link attached. (Thanks to "alephzain" for this awesome app)
(link to his thread http://forum.xda-developers.com/showthread.php?t=2130276 )
5. install it
6. open and click Boromir exploit
7. voila ur phone is rooted.
8. now reboot to see super su in app drawer
7. check it using root checker app from play store.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
click thanks if i helped..
CUSTOM RECOVERY SEE BELOW POST
Ctr , twrp, gravity box, link2sd
CUSTOM RECOVERY
Guys this has been developed by @yuweng @dhinesh77 and @carliv (Master Shifu)
Hats off to the guys for their awesome work.
Dont flash cwm recovery only flash CTR or TWRP recovery because our system format is UBIFS..
just download the CTR auto porting tool from the below thread
http://forum.xda-developers.com/showthread.php?t=1825722
Click to expand...
Click to collapse
(see for "Added on Jan 17, 2014
CTR v2.1 for MTK devices with ubifs ONLY " in the thread)
extract and run the program.
don't forget to install adb drivers before using the above tool. you can find the drivers here.. select other option in phone model.
http://www.mediafire.com/download/seg916ycv20cxj7/drivers.rar
ctr recovery is fully functional....
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
sorry TWRP recovery not working in this method
Hi here is the fully working TWRP recovery for Micromax A58
Quote:
DOWNLOAD recovery from
http://www.mediafire.com/download/9zpdq057829ltbj/recovery.img
Click to expand...
Click to collapse
OR
from the attachment below
STEPS TO INSTALL:
TO FLASH USING MOBILE
Click to expand...
Click to collapse
Flash using Mobileuncle tools (need a rooted phone)
-->Download the recovery and Put it in root of your SDCARD (ROOT OF SDCARD MEANS DON'T PUT THE FILE IN ANY FOLDER)
-->Open Mobile uncle tools and select Recovery Update
-->Flash recovery file
-->Done
Now reboot to recovery to check.....
Credits:
christiantroy
@yuweng
@Dees_Troy
@carliv
@dhinesh77
@dhinesh77
Source
https://github.com/dhinesh77/Team-Win-Recovery-Project
Click to expand...
Click to collapse
link to @dhinesh77 thread
http://forum.xda-developers.com/showthread.php?t=2615386
Click to expand...
Click to collapse
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
STEPS FOR REBOOTING INTO RECOVERY
1. switch of the mobile
2. remove the battery
3. replace the battery
4. hold the power button and volume up button until you see an android robot
5. now press the power button again to go into recovery.
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Steps for installing Gravity box
download the xposed module apk from the attachment or from
http://repo.xposed.info/module/de.robv.android.xposed.installer
Click to expand...
Click to collapse
1. After installing apk reboot the phone
2. open the app and select download option
3. now browse to find gravity box[JB] (i mean for jelly bean os)
4. download the latest version
5. install it
6.now go back to modules menu in xposed installer app and tick the gravity box option
7. now reboot your phone
8. enjoy using gravity box
https://www.youtube.com/watch?v=O7p2kW8-nnw
STEPS FOR MAKING LINK2SD WORK
Thanks to @abi.z for the scripts
Steps
1. Partition your sd card to have an ext4 2nd partition. 1 gb partiton max (adviceable) (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore. (dont open it)
3. Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. open terminal emulator app. and type the following command without quotes
"su" (press enter)
"mkdir /data/sdext2" (press enter)
"chmod 777 /etc/install-recovery.sh" (press enter)
5.Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
For people who want to use other partitions
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition number
then EXECUTE the script or REBOOT for the changes to take place.
INSTALLING VIPER EQUALIZER FOR QUALITY SOUNDS
I HAVE TESTED VIPER FOR ANDROID FX NOT XHiFI AND IS WORKING GR8 IN OUR PHONES
1. Download, extract and copy ViPER4Android_FX.apk (FX version v2.3.2.2 )to your device.
2. Install the apk as USER app or SYSTEM app is up to you.
3. Run FX app from app drawer, allow root access if asked.
4. When driver installation prompted, choose Yes.
5. V4A auto detects your CPU and show available driver modes
6. Choose your desired selection.
7. After installation done, Reboot device.
8. now open the app and select compatibility mode for audio to work.
TO DOWNLOAD THE APP GO TO THE BELOW FORUM
FORUM LINK:
http://vipersaudio.com/blog/?page_id=48
All stock items for micromax A58
< STOCK ITEMS
DRIVERS : http://www.4shared.com/rar/sWXxgEmM/Mobistel_Cynus_T1_Drivers_x86.html
STOCK ROM : https://drive.google.com/uc?id=0B6-h6iUVgfhJbWRIYW9MNmV0UzQ
STOCK BOOT.IMG : http://www.mediafire.com/view/id21q1m9a34b5dr/boot.img
STOCK RECOVERY : http://www.mediafire.com/view/g8tkf2a7qqv0zpu/recovery.img
SP_Flash_Tool : http://www.4shared.com/zip/xsHShvMw/SP_Flash_Tool_exe_v313320187.html/>
DONT FORGET TO CLICK THANKS IF I HELPED
Click to expand...
Click to collapse
confused!!!!
@dhinesh77 bro link2sd app is not working on my phone what about yours??
Do you know any way to fix it. it says mount script cannot be created, no such file or directory
Can we change ubifs to ext4 format.. Or is there any custom roms possible.
I have installed gravity box via xposed module and its really awesome on our phone.
Waiting for ur reply!!!!!:fingers-crossed:
alanvmathew said:
@dhinesh77 bro link2sd app is not working on my phone what about yours??
Do you know any way to fix it. it says mount script cannot be created, no such file or directory
Can we change ubifs to ext4 format.. Or is there any custom roms possible.
I have installed gravity box via xposed module and its really awesome on our phone.
Waiting for ur reply!!!!!:fingers-crossed:
Click to expand...
Click to collapse
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
dhinesh77 said:
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
Click to expand...
Click to collapse
Oh it hurtz.
Can we flash recovery using mobile uncle tools??? Or we can't? If we can then I all make a tutorial for it here.
alanvmathew said:
Oh it hurtz.
Can we flash recovery using mobile uncle tools??? Or we can't? If we can then I all make a tutorial for it here.
Click to expand...
Click to collapse
I tried with recovery manager it worked, didnt tried with mobileuncle app
dhinesh77 said:
I tried with recovery manager it worked, didnt tried with mobileuncle app
Click to expand...
Click to collapse
kewl ll make one then...... what happened to link2sd bro?? did u try?
or is there any other script that can work for us?
alanvmathew said:
kewl ll make one then...... what happened to link2sd bro?? did u try?
or is there any other script that can work for us?
Click to expand...
Click to collapse
@dhinesh77 bro link to sd any news?????
Rooted but Cannot enter Recovery mode
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
abi.z said:
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
Click to expand...
Click to collapse
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
abi.z said:
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
Click to expand...
Click to collapse
thanks guys it seemes uploaded is corrupted i will check this weekend , meanwhile try ctr recovery its expected to work 100%
---------- Post added at 06:31 AM ---------- Previous post was at 06:30 AM ----------
abi.z said:
I have even tried dd ing the recovery image provided to the recovery partition manually.write was successfull. But no hope.I doesnt come to recovery menu.VolUp+power comes to bolt logo ans then restarts and continue normal boot
Need your help !
Click to expand...
Click to collapse
alanvmathew said:
@dhinesh77 bro link to sd any news?????
Click to expand...
Click to collapse
Sry bro i dont have enugh space to make ext parttion on sdcard , so i cant able to check
@dhinesh77
Thnx dude..I was wondering wats wrong with my phone s recovery mode..
As mentioned in my prev post that ctr auto porting tool fails in last step too.tried on winxp.
Waiting for or next upload bro.thanks for your works
BTW will try ctr again toninght
Sent from my Micromax A58 using xda app-developers app
abi.z said:
Hi
I rooted my a 58 using FramRoot, installed gravity toolbox also.
However i try, Iam not able to get into recovery.
#Tried flashing using Mobile Uncle, it flashes and asks to reboot to recovery.But again boots into normal os.
On powering on with vol+ and power button it shows only new Bolt logo(white letters in green trapezium) and no android
I tried rebooting into recover with different tools but all same result.
# Tried running the CTRv2.1-ubifs.exe a no of times.
It detects my MT6572 SoC and asks for root rights on phone, but fails after issueing dd commands with the following message on pc screen "Error detected, cannot unpack recovery.img"
I had around 90mb free space in data partition.
#
This is what I could observe, if iam trying to get into recovery it shows bolt logo as said above, then black screen and again comes to bolt logo and continues a normal boot.
Tried vol- and power button. Took me to some chinese factory testing menu.I could test my device hardware and also could do a factory reset from that menu.But not idea how to get into recovery from there.
I have all the drivers installed and I am not a newbiew, has flashed a lot of recoveries and custom roms on diff devices.
I followed @dhinesh77 thread and the cat /proc/mtd command screenshot is attached.
I have no idea what iam missing here, If you need any details i can provide the same.Please help me
Click to expand...
Click to collapse
Did u install busy box in phone before proceeding. Try installing busy box. Then in ctr try manual porting option and use the stock recovery.IMG. if u did not take back up of stock.IMG I can share it with u. It will work I too had this problem... If u have any doubt ask me.
i am gonna share two roms with you u can use it.
T-09 version rom
http://www.adrive.com/public/RYVRp2.html
T-07 version rom
http://www.4shared.com/zip/wB64yz-vce/A58_T07_2_.html
extract the correct version of rom for your phone and use the recovery.img . you can see the version in about phone option or by removing the battery.
alanvmathew said:
Did u install busy box in phone before proceeding. Try installing busy box. Then in ctr try manual porting option and use the stock recovery.IMG. if u did not take back up of stock.IMG I can share it with u. It will work I too had this problem... If u have any doubt ask me.
i am gonna share two roms with you u can use it.
T-09 version rom
http://www.adrive.com/public/RYVRp2.html
T-07 version rom
http://www.4shared.com/zip/wB64yz-vce/A58_T07_2_.html
extract the correct version of rom for your phone and use the recovery.img . you can see the version in about phone option or by removing the battery.
Click to expand...
Click to collapse
Thanks dude.
@dinesh77 s post helped me to conclude the issue.
Your post led me back on track and thanks for uploading the roms. Although i dint download because of my limited conn speed, itll be of help to someone.
Here's how i solved the issue.
I checked unpacking my existing recovery image and it was corrupted.
I was having a problem since i flashed the corrupted recovery initially, and lateron ctr porting tool was not able extract the existing recovery details for porting.
So i got twrp recovery from your the mediafire link in the first post did a porting and then everything worked fine with ctr recovery.
twrp recovery was running, but backup functionality wasnt working.
Iam not able to use advanced restore from ctr recovery.
All othr functions works from ctr..
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
dhinesh77 said:
I didnt used link2sd so far,
We cant change ubifs to ext4 unless got kernel sources
still custom roms are distant dream because of low system partition memory
Click to expand...
Click to collapse
@alanvmathew
Good News bro, I have somehow managed to get link2sd working with fat32.Had to do a lot of trial and error with manual mounting and reformating and reformating..
Was after link2sd till 3:00am
In office now. Will try to reproduce the issues and soon come up with the correct solution for link2sd after iam home.
link2sd
abi.z said:
Thanks dude.
@dinesh77 s post helped me to conclude the issue.
Your post led me back on track and thanks for uploading the roms. Although i dint download because of my limited conn speed, itll be of help to someone.
Here's how i solved the issue.
I checked unpacking my existing recovery image and it was corrupted.
I was having a problem since i flashed the corrupted recovery initially, and lateron ctr porting tool was not able extract the existing recovery details for porting.
So i got twrp recovery from your the mediafire link in the first post did a porting and then everything worked fine with ctr recovery.
twrp recovery was running, but backup functionality wasnt working.
Iam not able to use advanced restore from ctr recovery.
All othr functions works from ctr..
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
@alanvmathew
Good News bro, I have somehow managed to get link2sd working with fat32.Had to do a lot of trial and error with manual mounting and reformating and reformating..
Was after link2sd till 3:00am
In office now. Will try to reproduce the issues and soon come up with the correct solution for link2sd after iam home.
Click to expand...
Click to collapse
Congratulation bro! And please share the procedure here so we can also get benefit of it. Thanks in advance.
Increase internal Memory !! Link2sd Working !! [Use Manual mount Script]
Steps
1. Partition your sd card to have an ext4 2nd partition. I used a second primary partition of 512mb (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore.
3. Mount /system read-write and Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. Using filemanager(root) goto /data and create directory sdext2. or mkdir /data/sdext2 using root terminal
5. Set permissions on the copied file using filemanager(root) as in screenshot or chmod 777 /etc/install-recovery.sh using root terminal.
6. Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Incase you want to test if link2sd will work or not with your current sdcard 2nd partition, issue the commands in terminal
su
mkdir /data/sdext2
mount -t ext4-o rw /dev/block/mmcblk0p2 /data/sdext2
or
mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition no.
!!eNJOY!!
abi.z said:
@dhinesh77
Thnx dude..I was wondering wats wrong with my phone s recovery mode..
As mentioned in my prev post that ctr auto porting tool fails in last step too.tried on winxp.
Waiting for or next upload bro.thanks for your works
BTW will try ctr again toninght
Sent from my Micromax A58 using xda app-developers app
Click to expand...
Click to collapse
It seems root access was denied for ctr auto port tool, hence why you failed, reinsure that you have running auto port tool under c:/ ; anyhow I will upload ctr compiled recovery too on this weekend sry or delay
dhinesh77 said:
It seems root access was denied for ctr auto port tool, hence why you failed, reinsure that you have running auto port tool under c:/ ; anyhow I will upload ctr compiled recovery too on this weekend sry or delay
Click to expand...
Click to collapse
@dhinesh77 Ya please upload so that others can use it.. If you want i can upload ported ctr recovery.
It was not root access causing problems,I had flahed the corrupted download to phone initially and then the recovery.img which ctr was reading from my phone was corrupted for autoporting tool to work on, and was failing while extracting the .img..
1 week old Bolt A58 with Root+Gravity+CTR+Link2sd
Everything is fixed now, and i will be gifting it to my father this weekend.
Thanks for help everyone
abi.z said:
Steps
1. Partition your sd card to have an ext4 2nd partition. I used a second primary partition of 512mb (ext3,ext4 fat32 confirmed working)
2. Install Link2sd from playstore.
3. Mount /system read-write and Copy attached install-recovery.sh to /etc/ using any file manager with root access.
4. Using filemanager(root) goto /data and create directory sdext2. or mkdir /data/sdext2 using root terminal
5. Set permissions on the copied file using filemanager(root) as in screenshot or chmod 777 /etc/install-recovery.sh using root terminal.
6. Done!! Reboot your system and check link2sd->Storage info to see the mounted partition details.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Incase you want to test if link2sd will work or not with your current sdcard 2nd partition, issue the commands in terminal
su
mkdir /data/sdext2
mount -t ext4-o rw /dev/block/mmcblk0p2 /data/sdext2
or
mount -t ext4 -o rw /dev/block/vold/179:2 /data/sdext2
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Make the following changes in the mount command in case you are using a different partition/filesystem
Open your install-recovery.sh and
Replace ext4 with ext2/ext3/vfat depending on you second partition.
If using a partition other than 2nd partition, Replace either mmcblk0p2 with mmcblk0p3 OR 179:2 with 179:3 or so on depending on your partition no.
!!eNJOY!!
Click to expand...
Click to collapse
WORKED.......!!!!!!! :laugh::laugh::laugh:
abi.z said:
@dhinesh77 Ya please upload so that others can use it.. If you want i can upload ported ctr recovery.
It was not root access causing problems,I had flahed the corrupted download to phone initially and then the recovery.img which ctr was reading from my phone was corrupted for autoporting tool to work on, and was failing while extracting the .img..
1 week old Bolt A58 with Root+Gravity+CTR+Link2sd
Everything is fixed now, and i will be gifting it to my father this weekend.
Thanks for help everyone
Click to expand...
Click to collapse
Mr.Carliv has updated his recovery version to 2.2 , ported just now and updated in main post , all bugs fixed in ctr recovery too :good:
This is a simple script that will convert almost any Galaxy Nexus EXT4 ROM to F2FS. The script will simply swap out the kernel (unless you plan to use an AnyKernel kernel) and edit the updater-script to replace EXT4-specific lines with F2FS-specific lines (unless you have /system formatted as EXT4, in which case the line that formats /system will be left as is). The included boot.img may be replaced with any gnex F2FS boot.img.
Also, for Windows only, @sergialess created a GUI conversion tool. It allows you to choose the ROM zip from any location, choose an alternate boot.img from any location, or even choose a flashable kernel zip from any location in order to extract the boot.img. It's pretty slick, so if you like it, show him some love! As of 7/7/14, the GUI has an option for APK deletion like the three script-based tools, but it's the only one that goes one step further and allow you to select which APKs to delete.
NOTE: If you have not reformatted your device for F2FS, you're not ready to use this tool yet. This tool will make a ROM F2FS-compatible, it will not convert your device to F2FS. To reformat your device to F2FS, start with posts #1 and #2 here: http://forum.xda-developers.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655
ROMs that have successfully converted and booted:
AOKP
AOSB
Carbon
C-ROM
Cyanogenmod
LiquidSmooth
Omni FML
Paranoid Android
Shiny (make sure to use EXT_to_F2FS_2014-07-07 or later and purge APKs)
SlimKat (make sure to use EXT_to_F2FS_2014-07-07 or later)
TREX
Vanir (make sure to use EXT_to_F2FS_2014-07-07 or later)
Click to expand...
Click to collapse
ROMs that have caused problems:
You tell me!
Click to expand...
Click to collapse
Alternative F2FS kernels:
cwm-DirtyV-SR-6.15.14-2-Unified.zip - modified by @osm0sis
fancy_kernel-tuna-4.4-r53.zip
SmittyV-UR-6.15.14_F2FS_discard.zip - modified by @ilgimmy
SmittyV-UR-6.28.14.zip - may conflict with some ROMs
Click to expand...
Click to collapse
Windows instructions:
1) Ensure you have .NET installed (required for GUI and find-and-replace tool).
2) Unzip the windows zip to any empty folder.
3) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder. (Requirement only for batch file, not GUI).
4) Run EXT4_to_F2FS_gnex.bat or EXT4_to_F2FS_gnex_GUI.exe.
Click to expand...
Click to collapse
Linux / Mac instructions:
1) Ensure you have sed, zip, and unzip installed. And note that this is a bash script.
2) Unzip the linux_mac zip to any empty folder.
3) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder.
4) cd into your converter folder
5) Run "chmod +x EXT4_to_F2FS_gnex.sh". This only needs to be done once.
6) Run "./EXT4_to_F2FS_gnex.sh"
Click to expand...
Click to collapse
Android instructions:
1) Ensure you have a zip binary, likely located at /system/xbin. If not, flash zip_binary_flashable.zip from recovery.
2) Ensure you have busybox. Stericson's 1.22.1 definitely works: https://play.google.com/store/apps/details?id=stericson.busybox. Others may not, try Stericson's before reporting problems.
3) Unzip the android zip to any empty folder on the SD card.
4) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder.
5) Open an Android terminal
6) Run "su" (there's problems with unzipping when not root for some reason)
7) cd into your converter folder
8) Delete boot.img if you're going to install an AnyKernel kernel after installing the converted ROM
9a) Run "sh f2fs.sh" if your /system partition is formatted F2FS
9b) Run "sh ext4.sh" if your /system partition is formatted EXT4
Click to expand...
Click to collapse
Mediafire downloads: http://www.mediafire.com/?m501v8um8nd1y
Google Drive mirror: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhVUt0QmFwUVFwYk0&usp=sharing
Changelog:
9/18/14: Windows GUI updated - Velvet is no longer purged, AnyKernel support, and EXT4 /system partition support.
9/15/14: Android version supports AnyKernel kernels and EXT4 /system partitions. Be sure to read steps 8 and 9 in the instructions.
9/14/14: Windows & Linux/Mac versions support AnyKernel kernels and EXT4 /system partitions. Window GUI has NOT been updated yet.
8/18/14: Velvet is no longer purged. All versions now include Fancy r54. Window GUI has NOT been updated yet.
7/15/14: Changed method of reading ROM ZIP name in Linux/Mac version. All versions now include Fancy r51.
7/11/14: Very minor change to Linux tool to make it compatible with the Mac terminal.
7/7/14: Windows (including GUI), Linux, & Android tools handle /data mounting (for SlimKat) and have option to purge unneeded APKs (for Shiny).
7/2/14: Added Windows GUI tool.
7/1/14: Spaces in the path are no longer a problem in the Windows version, added Linux and Android versions, included boot.img is SmittyV 6/28/14
6/25/14: Initial release, included boot.img is DirtyV 6/9/14.
Credits:
@bsmitty83, @osm0sis, @metalspring, and everyone else in the DirtyV thread who made F2FS possible: http://forum.xda-developers.com/galaxy-nexus/development/kernel-dirtyv-6-9-14-t2613655
@NABENDU1 for the grouper F2FS ROM conversion tool that inspired this: http://forum.xda-developers.com/show....php?t=2731666
@sergialess for the Windows GUI tool.
@boype for his Fancy kernel: http://forum.xda-developers.com/galaxy-nexus/development/kernel-fancy-kernel-r50-t2115590
@latenightchameleon for the idea to purge unneeded APKs from large ROM zips like Shiny.
@johansenmo for the assistance in making the Linux tool Mac compatible.
My other projects:
LiquidSmooth-OFFICIAL for maguro: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2667078
LiquidSmooth-OFFICIAL for toro: http://forum.xda-developers.com/gal...m-liquidsmooth-v3-1-kitkat4-4-3-toro-t2575560
LiquidSmooth-OFFICIAL for toroplus: http://forum.xda-developers.com/gal...m-official-liquidsmooth-kitkat-4-4-3-t2672510
LiquidSmooth-UNOFFICIAL for maguro: http://forum.xda-developers.com/gal...aguro-toro-t2793275/post53641446#post53641446
LiquidSmooth-UNOFFICIAL for toro: http://forum.xda-developers.com/galaxy-nexus/verizon-develop/rom-liquidsmooth-v3-1-toro-t2793284
LiquidSmooth-UNOFFICIAL for toroplus: http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-liquidsmooth-v3-1-toroplus-t2793281
LiquidSmooth-UNOFFICIAL for grouper: http://forum.xda-developers.com/showthread.php?t=2709385
F2FS Converter tools for grouper ROMs: http://forum.xda-developers.com/nexus-7/development/tool-grouper-ext4-to-f2fs-rom-converter-t2801653
Ting APNs to fix LTE: http://forum.xda-developers.com/galaxy-nexus/general/ting-flashable-zip-fixed-lte-android-4-t2428999
Verizon APNs to fix MMS: http://forum.xda-developers.com/android/software/tool-verizon-mms-apn-patch-t2833914
Click to expand...
Click to collapse
[poo]
~~
poo706 said:
This is a simple Windows batch script that will convert any Galaxy Nexus EXT4 ROM to F2FS. Thanks to NABENDU1 for the grouper script that inspired my gnex script: http://forum.xda-developers.com/showthread.php?t=2731666 . The script will simply swap out boot.img (i.e. the kernel) and edit the updater-script to replace EXT4-specific lines with F2FS-specific lines. The included boot.img is DirtyV 06-09-2014, but it may be replaced with any gnex F2FS boot.img.
Instructions:
1) Unzip EXT4_to_F2FS_gnex.zip to any empty folder, make sure there are no spaces anywhere in the path.
2) Place your EXT4 gnex ROM zip in the same folder, make sure there are no other zips in this folder.
3) Run EXT4_to_F2FS_gnex.bat.
Download: https://drive.google.com/folderview?id=0B_Yk7pLJ4-VhVUt0QmFwUVFwYk0&usp=sharing
[poo]
Click to expand...
Click to collapse
Magic
Works amazing, thanks!
T0RU said:
it works, hell yeah you deserve a big ass thanks from me
---------- Post added at 09:10 PM ---------- Previous post was at 09:09 PM ----------
Flashing now
Click to expand...
Click to collapse
pianistaPL said:
Magic
Works amazing, thanks!
Click to expand...
Click to collapse
Glad it worked out for you guys. I'd just throw a couple of thanks your way, but I used up my 8 first thing this morning.
[poo]
~~
T0RU said:
Odd I tried to make a f2fs for paranoid android but I keep getting this error PS it worked on shiny perfectly
HTML:
symlink: some symlinks failed
E: Error executing updater binary in zip '/sdcard/f2fsaospa.4.4.4.zip'
Error flashing zip '/sdcard/f2fsaospa.4.4.4.zip'
Click to expand...
Click to collapse
That is odd. A couple of people on this page http://forum.xda-developers.com/galaxy-nexus/help/f2fs-thread-questions-t2770735/page14 used my converter on PA without issue. Are you all using the same PA?
[poo]
~~
T0RU said:
RC2 and I do think it's because of the recovery (twrp2.7.1.0)
Click to expand...
Click to collapse
So the issue's not on my end then?
[poo]
Tried it with latest PA and Vanir and it worked just like a charm!
Then you for sharing Sir!
poo706 said:
So the issue's not on my end then?
[poo]
Click to expand...
Click to collapse
nope
ehh I still keep getting these errors
I moved back to 2.7.0.0
I tried to do this again on shiny, somehow it gives me the same error that I had with PA
any help?
T0RU said:
I tried to do this again on shiny, somehow it gives me the same error that I had with PA
any help?
Click to expand...
Click to collapse
Can you list what you do exactly? Must be something minor that you're missing out on.
it works very good thx
Just converted and flashed todays Vanir build and again without any issue!
:good::good::good::good::good:
T0RU said:
I tried to do this again on shiny, somehow it gives me the same error that I had with PA
any help?
Click to expand...
Click to collapse
I'm with Hetalk. I think something silly is going on, but I don't think it has to do with the conversion tool. (I keep wanting to refer to it as "my tool", but that somehow doesn't feel right.)
[poo]
Well well,
I flashed with fastboot this recovery --> http://www.trysoftcore.com/Recovery/TWRP-f2fs.zip
went to Advance->f2fs/ext4 switch->formatted all to f2fs (system ,cache and data)
adb sideloaded the rom (Just downloaded your tool and shiny rom again and did exactly what you said and then sideloaded it)
and after that I get this annoying message:
Code:
symlink: some symlinks failed
E: Error executing updater binary in zip '/sdcard/shiny.zip'
Error flashing zip '/sdcard/shiny.zip'
I named the zip file "Shiny.zip"
and that's all I did to get this error
T0RU said:
Well well,
I flashed with fastboot this recovery --> http://www.trysoftcore.com/Recovery/TWRP-f2fs.zip
went to Advance->f2fs/ext4 switch->formatted all to f2fs (system ,cache and data)
adb sideloaded the rom (Just downloaded your tool and shiny rom again and did exactly what you said and then sideloaded it)
and after that I get this annoying message:
Code:
symlink: some symlinks failed
E: Error executing updater binary in zip '/sdcard/shiny.zip'
Error flashing zip '/sdcard/shiny.zip'
I named the zip file "Shiny.zip"
and that's all I did to get this error
Click to expand...
Click to collapse
I think you need to change recoveries. I saw others in the dirtyv thread who ran in to problems with that recovery that supposedly is universal to all 3 gnex variants. Try the appropriate device-specific recovery under the all-in-one recovery.
[poo]
the 2.7.1.1 does not have a f2fs swice tap oddly enough
it only says EXT4 next to the twrp name
T0RU said:
the 2.7.1.1 does not have a f2fs swice tap oddly enough
it only says EXT4 next to the twrp name
Click to expand...
Click to collapse
Swice tap? What device do you have? Are you looking here for the recoveries? http://forum.xda-developers.com/showpost.php?p=49501604&postcount=1
[poo]
Hi there! I'm trying to build CM-12 for GT-I8160 based on TeamCanjica's CM-11. Actually, it has been compiled successfully with some hacks (I skipped imgdiff). But it bricked my phone after I flashed it via CWM. :crying:
I've unbricked my phone by flashing my backup of stock boot partition (mmcblk0p15) to "Kernel" partition via Heimdall. Then, my phone showed CM boot animation for a long time. (bootloop I think, maybe because of stock boot partition isn't compatible with it). And I use stock firmware for now.
I found that type of the boot partition (mmcblk0p15) of the stock differ with boot.img I've built.
Code:
$ file mmcblk0p15-boot (my backup of stock boot partition)
mmcblk0p15-boot: Linux kernel ARM boot executable zImage (little-endian)
$ file boot.img (boot.img I've extracted from cm-12-20141217-UNOFFICIAL-codina.zip)
boot.img: Android bootimg, kernel (0x40008000), ramdisk (0x41000000), page size: 4096
So, what are "Linux kernel ARM boot executable zImage" and "Android bootimg"? Where is the root partition (ramdisk) stored?
Is it okay to skip imgdiff? I think imgdiff is just for creation of OTA package. Am I correct?
I also found boot.img in out/target/product/codina (not in the zip file) which type is Linux kernel ARM boot executable zImage.
Is it the correct boot.img? I found that the content of that file is same with kernel file I found in the same folder. I'm afraid that the ramdisk is not included in it.
Sorry for my English n thank you very much.
Oh. All people wants to have cm12, but still 0 replies here.
I'm sorry, I can't help in this too... /
S.AMU said:
Oh. All people wants to have cm12, but still 0 replies here.
I'm sorry, I can't help in this too... /
Click to expand...
Click to collapse
Hi! It's okay, I've flashed out/target/product/codina/boot.img + gapps. It booted to CM-12 , freezed at the welcome screen n refused to boot again after I force-rebooted it :crying:. Unfortunately, ADB & recovery didn't work, so I didn't know much why it got freezed. Maybe I have to figure out how to compile a nice kernel with working ADB & recovery. Hahaha...
I was having problem with flashing cm12.1 zip.
I was getting error "error executing updater binary" in recovery.(Now i flashed it).
How i did it?........
1)I decompressed system.new.dat(which was in the zip) to ext 4...
2) then again decompressed ext4 to output folder(which was the old way to make zips).for more info http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952.
3)then edited updater script using refrence of updater script of mokee zip files(i was able to flash mokee51.1 roms).
voila it flashed successfully.
Now the que is why this happens?Am i the only one who faces this problem.
..God knows how frusted i was due to this.......
dtechgeek said:
I was having problem with flashing cm12.1 zip.
I was getting error "error executing updater binary" in recovery.(Now i flashed it).
How i did it?........
1)I decompressed system.new.dat(which was in the zip) to ext 4...
2) then again decompressed ext4 to output folder(which was the old way to make zips).for more info http://forum.xda-developers.com/and.../how-to-conver-lollipop-dat-files-to-t2978952.
3)then edited updater script using refrence of updater script of mokee zip files(i was able to flash mokee51.1 roms).
voila it flashed successfully.
Now the que is why this happens?Am i the only one who faces this problem.
..God knows how frusted i was due to this.......
Click to expand...
Click to collapse
On what recovery and version was this happened? And thanks for the link you gave, might be i need it in the future, if i have such an issue like yours.
presetz said:
On what recovery and version was this happened? And thanks for the link you gave, might be i need it in the future, if i have such an issue like yours.
Click to expand...
Click to collapse
I tried TWRP 2.8.6.0,philz.cwm....
I downloaded a samsung galaxy s22 Odin firmware and unpacked the zip and the AP tar file and then I un lz4'd the super.img, unsparsed it and then I ran lpunpack on the unsparsed image to get unreadable images
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
ze7zez said:
Have you used one of the following?
Extract system.img,vendor.img and product.img from super.img
After lots of search i found a way to extract those img file from super.img What is need? 1.Computer with linux os. extract zip file from this post and place your super.img in same location where you extract.. then run below cmd... simg2img...
forum.xda-developers.com
super_img_lpmake_lpunpack.zip | by MrWaehere for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
I have. I can get system.img out but I can't open it. I think it's a f2fs partition but I haven't found any tools that can extract files from it
It seems on newer firmware this method of unpacking and extracting system.img out of super.img no longer works. It seems now that when you extract system.img from super.img.raw it gives you a file that reads just as data and does not have the ext4 filesystem magic header bytes.
Have uploaded two screenshots to show how super.img.raw looks and how system.img looks after extraction from super.img. Any thoughts on this?
This firmware is being pulled from latest tar files for SM-S901U
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
kalexander7 said:
Update, am working on a way and almost got it now. Will probably create a post on this once done and link from here. If you dont hear back from me, i failed. :'(
UPDATE: had some luck following this guys tutorial although a little different was able to extract files. Still cant mount but much closer. Device is f2fs file system. The reason it's not working is most methods on xda are for ext4
How to Extract F2FS Image from Android Device Flash - Baremetallics
How to Extract F2FS Image from Android Device Flash
baremetallics.com
Click to expand...
Click to collapse
Is this also work for other's like erofs?
Mr Hassan said:
Is this also work for other's like erofs?
Click to expand...
Click to collapse
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
kalexander7 said:
I doubt it although it may be alike using same linux tools like fsck. Erm I'm still stuck on trying to get this f2fs image too mount. It seems corrupt and although I was able to extract libs and apks they're coming out corrupted. Anyone in the community have any knowledge in this area?
Click to expand...
Click to collapse
Bro samsung have many dev's to mount fsf2 and already many dude done
The erofs not possible
Mr Hassan said:
Bro samsung have many dev's to mount fsf2 and already many dude done
The **** is erofs
Click to expand...
Click to collapse
what?