Related
Motorola Defy Mini XT320/XT321 all-in-one script/utility
I've ported mattlgroff's DROIDRAZR all-in-one Script to the Motorola Defy Mini XT320/XT321. This will make life easier and it will do it for you.
Make sure you have fastboot mode if not please refer to this guide for fastboot but there is a fastboot checker in option 6 but it won't install fastboot for you.
Link: http://forum.xda-developers.com/showpost.php?p=36199694&postcount=3
Options available:
1. Root your Motorola Defy Mini XT320/XT321
2. Install 2nd-init/TWRP Recovery
3. Overclock installation
4. Unroot Device
5. Wipe Data/Factory Reset
6. Fastboot checker.
7. Exit Utility
Instructions:
NEW PACKAGE & instructions
1. Download the EXE file at http://www.mediafire.com/?c81fnrtrki65e9i
2. Double click on the exe.
3. Choose an option by entering a number from 1 to 7
OLD PACKAGE & instructions
1. Download package at [REMOVED OLD LINK]
Please Download the fixed package at http://www.mediafire.com/?krxtemrthsz5ier
EXE Version: http://www.mediafire.com/?0kwmx4whjj1ua8c
2. Extract the zip file making sure all the files are in the same place.
3. Click on the batch file named 'DefyMiniUtility.bat'
4. Choose an option by entering a number from 1 to 7.
Credits to:
- Bernd.Defy for overclock module and Guitwo2 for init.d script
- Guitwo2 and jkkk88 for TWRP and aweosomeabhjeet for 2nd-init
- DoOMLoRD for unroot script
- Mattlgroff for the original DROID RAZR all-in-one script
If anyone knows if I missed a member for the credits, please PM me. Thanks
Make sure press thanks if it works
Guys please don't repost it as your own work, otherwise I'll report it and you will get banned from XDA.
NOTE: If you have previously used the old EXE to install TWRP then please remove the old folders by using these instructions using cmd before using updated exe to install TWRP;
1.
Code:
adb shell
2.
Code:
su
3.
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock11 /system
4.
Code:
rm -R /system/bootmenu
Then use the updated exe to install TWRP.
NOTE: If you don't like TWRP, you can download Guitwo2's Permanent CWM at http://forum.xda-developers.com/attachment.php?attachmentid=1875373&d=1365682716
Temporary CWM Recovery: http://forum.xda-developers.com/attachment.php?attachmentid=1875299&d=1365680458
2nd-init does NOT work in CWM Recovery
Thanks to @Guitwo2 for CWM Recovery.
Instructions on how to install Permanent CWM Recovery:
1. Make sure stericson-busybox is installed
2. Put XT320_bootmenuV2.zip in the root of your sdcard
3. Reboot into fastboot mode by typing this command in cmd:
Code:
adb reboot bootloader
4. Then type this command in cmd:
Code:
fastboot boot recovery.img
5. Then use volume keys to navigate and power button to select option. Select install zip from sdcard, then select XT320_bootmenuV2.zip and select yes to install the zip file
6. Then reboot device by selecting reboot device now.
CWM 6 has a bug where it asks you to 'disable recovery flash' when you select reboot system now make sure you select NO or you will soft brick your device.
Changelog:
-v2 No need to mount /sdcard in CWM Recovery. Fixed TWRP installation issues.
-v2.0.1 Released an .exe version of script, to simplify installation
-v2.0.1.1 Fixed bootmenu.zip
This can install a custom recovery?
This can install a custom recovery?
Thank you
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
same problem... someone can fix it? please
fca.sjc said:
The root process worked for me. Now i can install link2sd and set up a swap partition.
I cant install TWRP and i think the reason is that the bat was having some problem to send that bootmenu.tar file to my sd card. I tried to send that file myself before starting the entire process and it didnt worked.
I took a picture of the error i'm getting . Thank you again, i was really mad about that low internal space xD
Click to expand...
Click to collapse
sfoot13 said:
same problem... someone can fix it? please
Click to expand...
Click to collapse
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Thanks
rootdefyxt320 said:
Ok, I've made a fixed script here. The error was that the sdcard is a directory so it will refuse to push files into it.
Here's the updated script below. Just put the .bat file in the same place as the other files.
Click to expand...
Click to collapse
Ty for the quickly answer.
Btw, my gsm network wasnt working after the root process. If the same thing happens to someone else, just do a master reset and it will work again.
pull command is working now
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
fca.sjc said:
That sdcard copy part is working now. The TWRP process is still not working for me. I tried to do myself the commands using the adb interface and when i use the command to intall the tar, i got the message 'tar: no space left on device" . I hope you can help me with that and i'm sorry about all this questions xD .
Click to expand...
Click to collapse
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
rootdefyxt320 said:
You must have more than 5MB free in your /system partition. Please move your apps to the /flex partition or delete the useless apps in /system.
Click to expand...
Click to collapse
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
sfoot13 said:
Thank u so much to everyone who make it possible xD
(can i do now a overclock to 720 without problems?)
Click to expand...
Click to collapse
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
rootdefyxt320 said:
Yes but it sometimes gets unstable so you should overclock to 700MHz which is the highest I got without reboots. pll2_l_val=73 gives you 700MHz.
Click to expand...
Click to collapse
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
sfoot13 said:
Thank u so much and TWRP doesn't work xD i have 8.5 mb free on system but it can't create the folders on bootmenu
Click to expand...
Click to collapse
I've released an .exe version of my script. This should work now .
Link: http://www.mediafire.com/?0kwmx4whjj1ua8c
Thank u bro and sorry but i can't overclock it to 700 =/
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
OFF TOPIC.
Congrats on your well deserved mention on the portal.
sfoot13 said:
i installed TWRP but it doesn't work and when i turn on my mobile it freezes on home screen :/ is a mess.... it's possible install it via recovery (temportal CWM)?
Click to expand...
Click to collapse
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
rootdefyxt320 said:
It worked for others but in your situation the only thing I can advise is to do a data wipe and relfash SBF file. Just go to Guitwo2's there to install permanent CWM.
Link: http://forum.xda-developers.com/showthread.php?t=2229233
Click to expand...
Click to collapse
:good: Working! Thank u so much, now i have CWM working on my defy mini, i'm really thankful, thanks again
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
sfoot13 said:
Hi, it's me again... i have a new trouble
i installed the xt320_bootmenu.zip (from this thread http://forum.xda-developers.com/showthread.php?t=2229233) the first time that i rebooted works fine, but the on the second reboot it doesn't work, then i went to data to check if test.log was there and here's the problem... no test.log...
init.d was working fine until that i did it, i guess that my phone have troubles making work init.d
some solution for this annoying guy? thanks in advance!
Click to expand...
Click to collapse
Looks like 97bootmenu deleted itself, please reinstall the CWM zip again and it should work.
[TOOL] [v3.2] [09NOV] Ubuntu Touch "system-image" Installer // w/o computers
# All credit goes to Ubuntu and contributors
ut-system-installer
I wanted to install Ubuntu Touch system-image (official, ro, OTA-enabled, for-sale-in-the-future) on my Galaxy Nexus, but there were some limitations and disadvantages to do so. It requires Ubuntu on my computer and completely wipes my device. Compared to cdimage-touch, which one can install easily with his/her phone, system-image is hard for some people to try, so I made a simple recovery-flashable zip with shell scripts to install it without computer and losing data. It downloads and installs system-image on your device(officially supported ones only).
What is does:
The same thing as doing
Code:
phablet-flash ubuntu-system --channel devel --no-backup
but without wiping the device, so
-Download files for installing Ubuntu Touch system-image (half-automatically)
-Install it on your device (supported ones by Canonical)
Supported Devices:
-Galaxy Nexus (maguro, toro, toroplus)
-Nexus 7 (grouper, tilapia)
-Nexus 4 (mako)
-Nexus 10 (manta)
Downloads:
http://d-h.st/users/zittoro/ut
Do not use anything in wip folder.
* This will install a CWM-based recovery from Ubuntu, and your device could brick but will not be compensated. *
How-to:
1. Download the zip.
2. Unzip it in /sdcard/Download/ut
3. Move or copy ut-system-dl(read "Arguments for "ut-system-dl"" in second post for options) to /data. Then run the script with root(su). You can just type these in terminal instead of doing this step manually (You need busybox and su installed)
Code:
su
cp -a /storage/emulated/0/Download/ut/ut-system-dl /data
sh /data/ut-system-dl
4. Zip everything in /sdcard/Download/ut
5. Flash it in recovery and reboot recovery (Just use the default install menu at home if you are using special recoveries like MultiROM)
6. Enjoy Ubuntu Touch
Bug reports: post your /sdcard/Download/ut/ut-system.log, /cache/recovery/last_log, and copy of the error if possible
Changelogs:
Code:
[b]09NOV2013[/b]
v3.2
-Added official UT disclaimer link
-Cleaner code
[b]07NOV2013[/b]
v3.1
-Support for "generic customization" channels
[b]03NOV2013[/b]
v3
-Support for "*-customized" channels
-More consistent and easier way of configuring files names to download
v2.2
-Download the recovery image properly as saucy-named doesn't exist in the path anymore. --Thanks to @pildoc for reporting.
[b]21OCT2013[/b]
v2.1
-Log file support to the installation script; still need recovery log because of "system-image-installer"
-Support for trusty-related channels
-Workaround for delta images when device files are the same
-Dropped support for old-channel device images
-Workaround for non-patched recoveries
-Show the actual device names rather than codenames to avoid confusion
[b]19OCT2013[/b]
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
[b]18OCT2013[/b]
v1.2
-Fix for script error
-Aborts installation if script fails
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad:(
-Added log file: ut-system.log
[b]16OCT2013[/b]
v1
-Initial
Arguments for "ut-system-dl":
-$1: -auto: default for script, automatically detects the device's codename using the value for "ro.build.product"
-DEVICE_NAME: images for DEVICE_NAME devices
-$2: -full: default for script, full images used for initial installation
-delta: delta images used for updates(OTA)
-$3: -CHANNEL: use CHANNEL channel to download images, default "devel"
-$4: -BUILD_NUMBER: build number of image
I dont get it
Sent from my Nexus 4 using xda app-developers app
gazhead said:
I dont get it
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
It basically installs the recommended version of ubuntu touch
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
hockeyadc said:
Looks like your path is wrong? If its going into download/ut shouldn't it be:
su
cp -a /storage/emulated/0/download/ut /data
sh /data/ut-system-dl
Click to expand...
Click to collapse
Dang I made a mistake
Zittoro said:
Dang I made a mistake
Click to expand...
Click to collapse
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
hockeyadc said:
Haha no problem. I'm trying this out on my phone(Maguro) and it gets stuck at connecting to the server. Any ideas? Just a ton of people trying to download right now?
Click to expand...
Click to collapse
Can you get a screenshot for me?
Zittoro said:
Can you get a screenshot for me?
Click to expand...
Click to collapse
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
hockeyadc said:
Actually, i just tried again and its working. 53 min ETA but its ok. When I zip this and flash it, does it remove my current recovery? How do I go back to my current rom in the future?
Click to expand...
Click to collapse
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Zittoro said:
It installs a CWM-based recovery with some tweaks and workout for system-image installation. Since it doesn't even touch your system partition, you can just flash an android kernel and get back to android.
Click to expand...
Click to collapse
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
hockeyadc said:
Nice! That makes it pretty easy. Now we just need a way to dual boot lol. Perhaps a program that allows you to select android or ubuntu, and upon android selection it flashes a new kernel?
Click to expand...
Click to collapse
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Zittoro said:
It's already possible on gnex.
http://forum.xda-developers.com/showthread.php?t=2480404
This kernel has tri-boot option for android and ut and recovery dual-boot using its recovery
Click to expand...
Click to collapse
Awesome!
hockeyadc said:
Awesome!
Click to expand...
Click to collapse
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Zittoro said:
Hey did you get it installed successfully? Some people in a different community say it doesn't. Did it boot into a new recovery when you rebooted it?
Click to expand...
Click to collapse
I haven't tried yet. I realized how many apps I need and use on a daily basis, so I would rather not install it yet. Just gonna wait it out until Ubuntu is more complete.
Changelogs:
18OCT2013
v1.1
-Recovery installation fix; it wasn't moved to the correct path, my bad
-Added log file: ut-system.log
v1.2
-Fix for script error
-Aborts installation if script fails
Blur
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
subaash said:
can you guys explain to me step by step in doing so. Sorry for being a noob. i want to learn how to so that i can help others and also improve my knowledge..
Click to expand...
Click to collapse
1. Download the zip from the link
2. Unzip it to the specified directory on your phone (you can do this with a file explorer app)
3. Download a terminal app and copy and paste the "code" into it.
4. If you get an error, post your /sdcard/Download/ut-system.log. If you don't, zip everything in the specified folder and flash it in recovery
5. Reboot recovery right after the installation
Changelogs:
19OCT2013
v2
-Add support for deciding which build number to download --$4
-Fix delta image download
-Mount before extracting files
Will this work with kulturom(nexus7) AS secondary ROM?
Wysłane z mojego Nexus 7 przy użyciu Tapatalk
o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log
sysKin said:
o/
Trying to flash F4k's awesome kernel here http://forum.xda-developers.com/showthread.php?t=2636890
(I'd post there but it won't let me before I have 10 posts).
I'm using ROM manager: Install ROM from SD card - I select the zip from my SD card - confirm.
However, it doesn't seem to work. What seems to happen is that wlan configuration files (system/etc/firmware/wlan/prima/) do flash, but kernel remains unchanged. Options - About Device says that kernel version is 3.4.0-1266356 which is what my Mini came with.
As a result I end up with old kernel and broken wlan.
Recovery does report that "some operations fail". Attaching recovery.log
Halp? Am I doing this wrong? Should I apply the .zip using some other tools?
Thanks!
[edit] attachment is invisible (yet?) so here's an alternative copy of recovery.log: https://www.dropbox.com/s/7g2378naa4bhbdy/recovery.log
Click to expand...
Click to collapse
What ROM are you using?
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.
TNCS said:
What ROM are you using?
Click to expand...
Click to collapse
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
TNCS said:
Installation is suppose to be simple with CWM:
1. Boot to CWM
2. Wipe cache and dalvik cache
3. Install kernel ZIP (do not extract the zip or modifiy it)
4. Reboot.
Click to expand...
Click to collapse
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
minzip: Can't create containing directory for "/system/etc/init.d/90hardlimit": Not a directory
set_perm: chown of /system/etc/init.d/90hardlimit to 0 0 failed: Not a directory
set_perm: chmod of /system/etc/init.d/90hardlimit to 755 failed: Not a directory
script aborted: set_perm: some changes failed
Click to expand...
Click to collapse
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.
sysKin said:
Stock.
By which I mean I9195TDVUAMH1, the stock for Australian I9195T.
Should be fine, right? Or did I misunderstand?
Yup, that's effectively the same thing I did (only I used ROM Manager app to avoid pressing volume down button lol). Fails on the same assert and produces that same recovery.log as I've shared.
Looking at this, should the script mkdir /system/etc/init.d? Or should I simply do it beforehand? It's not there on my stock filesystem.
Click to expand...
Click to collapse
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.
TNCS said:
I assume you have rooted your phone.. I have no idea why it does that, I think you should redirect the quuestion at F4k's post for stock ROM.
Click to expand...
Click to collapse
Thanks for your help TNCS. Five more posts and I'll be able to post in that thread
In the meantime I hope F4k doesn't mind a private message.
TWRP Recovery
For Galaxy Gio
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
BUGS:
If you have found a bug, please consider posting it here.
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
SPECIAL NOTE:
This is the first build of TWRP and may have some unknown bugs. I take no responsibility of your devices. This is "testing" phase (for some days only). Help in testing if you wish to otherwise stay away until a final release. Don't post back here that: "You destroyed my phone", "You are cheating", "You are playing with my device".
One more thing, we are using androidarmv6 sources and if you are asking for help on IRC channel mentioned above then please mention there that: "we are not using CM or OMNI sources, we are using androidarmv6 sources".
CREDITS:
TeamWin: For this awesome open-source recovery.
androidarmv6 team: To make all these possible.
@chraso: For hosting & providing compatible flags.
Me: Compiling work.
CHANGELOG for 2.7.0.0:
-Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
-Allow sideloading from /tmp on encrypted devices
-Check for a crypto footer before asking for a password to prevent user confusion
-Additional checks for validity to auto generated backup names
-Text wrap in the console output
-Proper caps lock support in the keyboard
-Mouse support via USB OTG for devices with a broken digitizer
-Improve scanning of storage locations for OpenRecoveryScript
-Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
-Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
-Update SuperSU to 1.93 and improve installation process
-Added selinux contexts restoration to fix permissions
-Load RTC offset on Qualcomm devices to fix the date/time in recovery
-USB Mass Storage fixes Add SELinux support checking
-Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
-Add 4.4 decrypt support
-Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
-Various SELinux fixes and bug fixes.
DOWNLOAD:
https://drive.google.com/file/d/0B5c3gpyMBJusUzlJSW1HaFNNV00/edit?usp=sharing
INSTALLATION / UPDATING:
-From the above download link, you'll get a 'recovery.img' file.
-Put that file at the root of sdcard (means, not in any folder)
-Now, open Terminal Emulator and give this command:
Code:
su
You'll be asked to grant superuser permissions, grant them.
-Now, give this command:
Code:
flash_image recoveryonly /sdcard/recovery.img
And wait for 2-3 seconds until it jumps to a new line. Now, close Terminal Emulator.
-Now, normally reboot to recovery and enjoy new recovery!
For download: See post #9
To understand what happened?: See post #8
Install the zip file (from post #9) normally and enjoy fully working TWRP.
About the current build:
-STABLE (from post #9)
@Bhargav97
This one is not rebooting to system too. Power off isn't working either, keeps on rebooting to recovery
Looking forward to fixing this, as I like it a lot more and I'm on OMNI rom. With this i'll be able to flash OTA automatically.
Thanks in advance!
is it possible to install on stock gingerbread 2.3.6 firmware?
@Bhargav97
Sorry for disturbing you. Are you planning any updates on this? Waiting so much ^_^ sorry for eta
belyava said:
@Bhargav97
Sorry for disturbing you. Are you planning any updates on this? Waiting so much ^_^ sorry for eta
Click to expand...
Click to collapse
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Bhargav97 said:
My PC is busy again and I can't say when I'll get time but I'll be releasing update soon.
If you want it badly then just do:
Unpack the recovery.img (of this TWRP)
Now, unpack the recovery.img of PhilZ Touch Recovery.
Now, replace the "KERNEL" file in TWRP's unpack from the PhilZ Touch Recovery's unpack.
Now, repack the TWRP's unpack.
Note: If you don't know how to unpack/repack recovery.img file, just Google and you'll learn it in few minutes. It's very easy.
You can use that until my official release.
Click to expand...
Click to collapse
:victory: YAAAAAY!!!! I'm happy like a little kid on Xmas))))) I did it! Now it's rebooting to system properly! Thanks for the instructions!!!
I'll post it here untill you make one
:victory: YAAAAAY!!!! I'm happy like a little kid on Xmas))))) I did it! Now it's rebooting to system properly! Thanks for the instructions!!!
I'll post it here untill you make one
Click to expand...
Click to collapse
can i flash Cm7/9/10.1/11 with This recovery?
error
kaiserlourdes said:
can i flash Cm7/9/10.1/11 with This recovery?
Click to expand...
Click to collapse
When I try to flash cm11, it gives an 'updater script error.(cm11-rc9gio) any help?
s4meq said:
When I try to flash cm11, it gives an 'updater script error.(cm11-rc9gio) any help?
Click to expand...
Click to collapse
You need a TLS supported to flash CM11 (androidarmv6) builds later than 22/07/2014. I haven't added that support in TWRP(nor do I plan to).
You can find TLS supported CWM recoveries on AndroidARMv6 Jenkins.
If you want TLS support in TWRP, you can replace kernel in TWRP from the TLS supported CWM recoveries (I'm not gonna do it).
P.S. TWRP is not by @belyava. I and @chraso made it. Belyava helped in unpacking/repacking the correct kernel from my PhilZ Recovery. You might want to correct up your signature (?).
thx
Bhargav97 said:
You need a TLS supported to flash CM11 (androidarmv6) builds later than 22/07/2014. I haven't added that support in TWRP(nor do I plan to).
You can find TLS supported CWM recoveries on AndroidARMv6 Jenkins.
If you want TLS support in TWRP, you can replace kernel in TWRP from the TLS supported CWM recoveries (I'm not gonna do it).
P.S. TWRP is not by @belyava. I and @chraso made it. Belyava helped in unpacking/repacking the correct kernel from my PhilZ Recovery. You might want to correct up your signature (?).
Click to expand...
Click to collapse
Thanks... unfortunatley no mentoin of gio recoveries. Maybe I'm stuck with cm7. Plus none of the recoveries are for gio.
Maybe I'll try [URL="/http://forum.xda-developers.com/showthread.php?t=2649101&page=3#post54833652[/URL] except that it is slow
s4meq said:
When I try to flash cm11, it gives an 'updater script error.(cm11-rc9gio) any help?
Click to expand...
Click to collapse
i flashed my cm10.1 w/ this recovery
http://forum.xda-developers.com/showthread.php?t=2691050
s4meq said:
Thanks... unfortunatley no mentoin of gio recoveries. Maybe I'm stuck with cm7. Plus none of the recoveries are for gio.
Maybe I'll try [URL="/http://forum.xda-developers.com/showthread.php?t=2649101&page=3#post54833652[/URL] except that it is slow
Click to expand...
Click to collapse
TLS supported cwm recovery for gio.
http://jenkins.androidarmv6.org/vie...perimental/1056/artifact/archive/recovery.img
Ansh2000 said:
TLS supported cwm recovery for gio.
http://jenkins.androidarmv6.org/vie...perimental/1056/artifact/archive/recovery.img
Click to expand...
Click to collapse
a little too late, bro
a posted a flashable version of this earlier here
http://forum.xda-developers.com/showpost.php?p=54754255&postcount=534
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]