Related
I've put together a rooted version of the stock 6.2.1 update if anyone wants to have at it. I flashed this on my own Fire with TWRP and it boots and runs fine, but I haven't done any other testing. Shouldn't need to wipe /data if you're coming from a 6.2 system, not sure about other ROMs like CM. Of course, I highly recommend you make a backup before flashing (good habit, and all that). To install just put it onto your Fire's /sdcard partition, boot into TWRP and install the zip. Note that TWRP will complain that it can't find the /misc or /sd-ext partitions. This is normal, those partitions don't exist on the Fire, but it won't affect the installation.
I downloaded the stock zip from the link in this post: http://forum.xda-developers.com/showpost.php?p=20509203&postcount=91 and then I changed the following from the stock zip file:
Removed the bootloader and recovery.img updates
Removed the backup_data.zip because it doesn't make sense, really (it looks like it just extracts to /backup/, but if you flash it it will wipe your /data partition?)
Added busybox, Superuser and the su binary. Should be properly symlinked and permissions set correctly.
Modified the updater-script for the above things.
Additionally, if you have the Market installed you may need to re-install it after updating since Amazon didn't do this as a patch - it just formats /system and replaces it. If you updated the Market manually then the newer version should survive in /data/app. Also, if you installed any custom frameworks or libraries (e.g. the maps framework to use Google Currents and whatnot) then you'll need to reinstall those. Basically, anything you added or modified on /system will be gone.
Edit: Thanks sadlius for pointing me to dsixda's kitchen! I've added a version with an unsecure boot image (so you get root by default on a shell). I'll leave the old one in case anyone would prefer the secure boot image. I've also uploaded the boot image itself for anyone who might have already flashed the secure 6.2.1 zip. I tried it with fastboot and it booted up fine, so you can test it first with:
Code:
fastboot boot 6_2_1rootboot.img
If it works, you can flash it (permanently overwrites your current boot partition) with:
Code:
fastboot flash boot 6_2_1rootboot.img
Downloads
MOD EDIT: Links no longer valid so removed.
Multiupload, courtesy sadlius:
update-6.2.1-rooted-secureboot.zip
Stock rooted update 6.2.1, secure boot image
update-6.2.1-rooted-unsecureboot.zip
Stock rooted update 6.2.1, unsecure boot image
Multiupload, courtesy intel352 (md5's should be the same):
update-6.2.1-rooted-secureboot.zip
Multiupload:
6_2_1rootboot.img Unsecure 6.2.1 boot image
Original Downloads:
Removed these so Dropbox won't yell at me anymore ​
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.
You sir are a good Man....
sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
But I think I know what the problem is. Will attempt again in a few minutes. Or as soon as TWRP relinquished control of my KF back to me.
Click to expand...
Click to collapse
I got the "Cannot load volume /misc!" error, too, but it seems to be okay anyway. The KF simply doesn't have a /misc partition.
Curious that it can't open the zip, though, but I'll wait until after your second attempt to try troubleshooting.
sadalius said:
First attempt at installing I get:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
Click to expand...
Click to collapse
I have seen the same errors when I installed TWRP. It didn't seem to make a difference to it loading.
All but the last line.
E:Unable to open zip file.
Click to expand...
Click to collapse
I think that is the real error.
I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?
isn't 6.2 is latest ? where did 6.2.1 came from?
HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!
sadalius said:
I got it figured out. Somehow, the file was corrupted when I transferred it to the KF. Deleted it and re-transferred, it took it that time. Will report any positives or negatives once I get back to the actual OS and play around with it.
Thanks a bunch!!
---------- Post added at 02:28 PM ---------- Previous post was at 02:20 PM ----------
Yes. Everything I've tried so far works great!!
I do have one question though. I used to cook my own roms from OEM releases back when I had an HTC hero. May I ask what you used to root this with?
Click to expand...
Click to collapse
I do it manually. The update had a .bin extension but it was really a .zip, so I renamed it, extracted it, and made the modifications I wanted (like adding su/Superuser). Then I just re-zipped it.
Don't know if it's the most "efficient" way to do it, but it's straightforward enough and it's how I've always done it...
Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.
tes5884 said:
HI,
is there someway for me to flash this using fastboot? Because im stuck in fastboot and can't get out of it!
Click to expand...
Click to collapse
Edit: Pointed out in another post - the system image might be too big to flash via fastboot (like I said, I've never actually tried to use these). If you can get into fastboot you can try flashing a recovery, though, and then use that to try dd'ing the system image over or something.
Edit 2: Took down links since I exceeded my Dropbox bandwidth.
Can anyone verify this works? I mean the 6.2.1 pre rooted update zip
Sent from my Triumph using XDA App
dueltothedeath said:
Can anyone verify this works?
Sent from my Triumph using XDA App
Click to expand...
Click to collapse
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.
sadalius said:
Yes, I can. Works pretty well too. You'll get some error messages, but those shouldn't be an issue. When I installed it those error messages kind scared me, but once someone explained them, I felt a little better.
Click to expand...
Click to collapse
Anychance you could explain them to me? Working for me as well just curious what they mean.
sadalius said:
Wonder if dsixda's android kitchen would work on it. If it would, it would automatically make the boot.img unsecured through the root process. Not sure if it will handle it though.
Click to expand...
Click to collapse
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!
fbm111 said:
Anychance you could explain them to me? Working for me as well just curious what they mean.
Click to expand...
Click to collapse
When I first tried to install I got these error messages:
E:Cannot load volume /misc!
E:Cannot load volume /misc!
E:Unable to stat '/sd-ext/.'
E:Cannot load volume /misc!
E:Unable to open zip file.
since the kindle fire does not have a /misc volume or /sd-ext/ partition, it would give those errors. Those are nothing to worry about. The last error, Unable to open zip file was a real error, but it was cause when I transferred the file to flash to the KF, it got corrupted somehow. I just deleted it from the kindle using file expert and re-transferred it then tried flashing again. All was well at that point. I still got the cannot load volume /misc! and unable to stat '/sd-ext' but like I said, those do not exist on the kindle, thus the messages. But it still installs correctly.
---------- Post added at 05:05 PM ---------- Previous post was at 04:49 PM ----------
eldarerathis said:
Maybe I'll look into that tonight or tomorrow when I've got some time. I actually didn't know that the kitchen created an unsecured boot image for you. Thanks!
Click to expand...
Click to collapse
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.
I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.
sadalius said:
I took a quick look at it with your rom. It recognizes everything you've done to the ROM thus far. Have a look:
Android OS version : 2.3.4
Device : blaze
Model : Full Android on Blaze or SDP
ROM Name : L27.12.1-P1_QUANTA_20110422_quantaonly-1027-gefdcdf8
Rooted (Superuser.apk + su) : YES
Rooted (unsecured boot.img) : NO
BusyBox installed : YES
BusyBox run-parts support : NO
Apps2SD (Apps to EXT) enabled : NO
/data/app enabled : NO
Custom boot animation allowed : NO
Nano text editor installed : NO
Bash shell support : NO
/system/framework is deodexed : YES
/system/app is deodexed : YES
radio.img found : NO
ROM will wipe all data : NO
I don't have time to try it out with the stock rom, if I get time tomorrow I'll give it a go to see if it will work with it or not to make the boot.img unsecured. This maybe just what the doctor ordered to keep a stock rooted rom.
Click to expand...
Click to collapse
I just tried using dsixda's kitchen to modify the boot image and it looks like it worked. I can boot it in fastboot at least! I'm going to package it up and try flashing it for some testing. Thanks a lot!
neilrl79 said:
I flashed it and I don't really notice much of a difference, although my android market still works even tho this update obviously removed it as a system app but the update in /data/app still works.
Click to expand...
Click to collapse
It seems like a lot of little changes, so far. You can remove things from your carousel by long pressing them, and you can restrict certain access to your one-click and stuff. It also looks like the "Device" menu in settings got a little facelift because it lists "Application Storage" and "Internal Storage" separately (which I don't think it did before).
I flashed 6.2.1 unsecured .zip via twrp and received two E:Cannot load volume /misc! errors. I then wiped cache and dalvik, and booted up. Everything including Voodoo OTA root works fine. As you said though, google market was obliterated. I am about to put it back.
Edit: after sticking vending.apk back in /system/app and fixing permissions it appears everything is 100% back to order including market and running 6.2.1. I can't thank you enough. 6.2.1 feels much snappier, although it might be a placebo effect.
does this work if i am already on 6.2.1?
I'm using cm 7.2.0-buzz ,
2.3.7
Kernel Version: 2.6.35.14-nFinity [email protected] #1
Radio[Baseband version]: 13.45.55.24H_3.35.15.31
My GPS isn't working.
Please help me!
Gratitude in advance
Flash the newest radio.
You can find it in the complete wildfire index
Sent from my HTC Wildfire using Tapatalk 2
How to Flash the latest radio?
Installing the zip file through recovery mode?
[Sorry, but I really don't know how to do this!]
lo2ay said:
Flash the newest radio.
You can find it in the complete wildfire index
Sent from my HTC Wildfire using Tapatalk 2
Click to expand...
Click to collapse
Download the newest radio driver in the "Index" thread in the dev section. Then flash it in CWM 2.5.x.x
The latest ends with '20.10'
To get temp. CWM use the update1.zip in the 'Index' thread or use Rom manager to install CWM 2.5.x.x and reboot to recovery by rom manager.
I have downloaded the latest radio, but how do I "flash" it?
Hazou said:
Download the newest radio driver in the "Index" thread in the dev section. Then flash it in CWM 2.5.x.x
The latest ends with '20.10'
To get temp. CWM use the update1.zip in the 'Index' thread or use Rom manager to install CWM 2.5.x.x and reboot to recovery by rom manager.
Click to expand...
Click to collapse
ka9090 said:
I have downloaded the latest radio, but how do I "flash" it?
Click to expand...
Click to collapse
all steps
open rom manager
-menu: all recovery
-install 2.5.xx, in the first line you will find recovery installed 2.5.xx
then, from the menu: install rom
-looks for radio
-Install
the wildfire reboot and run the intallation after you have flashed the radio.
I think if you have a backup of a ROM with working GPS, it is easier and you know works to restore the rom, turn on the GPS (I turn on all connections) to enter in recovery and flash again CM7.
Thank you!
quack75 said:
all steps
open rom manager
-menu: all recovery
-install 2.5.xx, in the first line you will find recovery installed 2.5.xx
then, from the menu: install rom
-looks for radio
-Install
the wildfire reboot and run the intallation after you have flashed the radio.
I think if you have a backup of a ROM with working GPS, it is easier and you know works to restore the rom, turn on the GPS (I turn on all connections) to enter in recovery and flash again CM7.
Click to expand...
Click to collapse
hi everyone, I also have similar issue.
at first gps doesn't work at all, and after flashing radio 20.10 with android flasher
now the gps icon in status bar appear when I open google maps or gps test.
well, today is cloudy but it seems that the gps is not locking or even seeing any satellite.
I wonder if my gps is actually still not working or this is different issue?
I just root my phone last night and this is my first flashing experience with wildfire so I don't have any backup rom..
I tried gps patch to modify gps.conf but I don't see any improvement..
thanks in advance for your response..
Don't worry.
It's just the cloudy sky.
Go out when the skies are clear and just let the gps lock your own location once.
After that, it will start working smoothly.
-Rif- said:
hi everyone, I also have similar issue.
at first gps doesn't work at all, and after flashing radio 20.10 with android flasher
now the gps icon in status bar appear when I open google maps or gps test.
well, today is cloudy but it seems that the gps is not locking or even seeing any satellite.
I wonder if my gps is actually still not working or this is different issue?
I just root my phone last night and this is my first flashing experience with wildfire so I don't have any backup rom..
I tried gps patch to modify gps.conf but I don't see any improvement..
thanks in advance for your response..
Click to expand...
Click to collapse
BTW, can you please explain me how to do this?
http://forum.xda-developers.com/showthread.php?t=1447591
Gratitude in advance
ka9090 said:
Don't worry.
It's just the cloudy sky.
Go out when the skies are clear and just let the gps lock your own location once.
After that, it will start working smoothly.
Click to expand...
Click to collapse
yeah I hope so..
well then, now I'll just enjoy my new rom and maybe when the sky is clear I can have my gps locked :fingers-crossed:
ka9090 said:
BTW, can you please explain me how to do this?
http://forum.xda-developers.com/showthread.php?t=1447591
Gratitude in advance
Click to expand...
Click to collapse
hm, basically to apply any of that patch you only have to copy the files to /system/etc in your phone..
if you download one of the patch in that thread, you will get .zip file containing gps.conf and SuplRootCert (if exist).
there are various ways to copy those files such as using ES File Explorer, Root Explorer, or other similar apps.
but personally I used terminal emulator.
1. copy those files to a folder in your sd card
2. open terminal emulator and type
Code:
su
mount -o remount,rw /system
cp /system/etc/gps.conf /mnt/sdcard <backup your original gps.conf in case you will need to restore it>
cp /mnt/sdcard/anyfolder/gps.conf /system/etc <change anyfolder with the name of your folder>
cp /mnt/sdcard/anyfolder/SuplRootCert /system/etc <you don't have to type this line if this file didn't exist>
mount -o remount,ro /system
3. exit and maybe you need to reboot.. good luck
Lol. This seems kinda difficult. Thanks anyway
-Rif- said:
yeah I hope so..
well then, now I'll just enjoy my new rom and maybe when the sky is clear I can have my gps locked :fingers-crossed:
hm, basically to apply any of that patch you only have to copy the files to /system/etc in your phone..
if you download one of the patch in that thread, you will get .zip file containing gps.conf and SuplRootCert (if exist).
there are various ways to copy those files such as using ES File Explorer, Root Explorer, or other similar apps.
but personally I used terminal emulator.
1. copy those files to a folder in your sd card
2. open terminal emulator and type
Code:
su
mount -o remount,rw /system
cp /system/etc/gps.conf /mnt/sdcard <backup your original gps.conf in case you will need to restore it>
cp /mnt/sdcard/anyfolder/gps.conf /system/etc <change anyfolder with the name of your folder>
cp /mnt/sdcard/anyfolder/SuplRootCert /system/etc <you don't have to type this line if this file didn't exist>
mount -o remount,ro /system
3. exit and maybe you need to reboot.. good luck
Click to expand...
Click to collapse
ka9090 said:
BTW, can you please explain me how to do this?
http://forum.xda-developers.com/showthread.php?t=1447591
Gratitude in advance
Click to expand...
Click to collapse
Basically it is a patch to speed up the AGPS (with active connection) and it works I tried it with the GPS STATUS application
some useful sections of tread:
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
So it is really very easy :victory::victory:
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.
Ace 2 Gt-i8160L LATIN. How to install CM?
When I install CM, don't wok sim-card and not IMEI.
Restore IMEI don't helped.
This is modem or hw problems, i think.
Sorry my english is bad.
...
Replace tee folder in rom zip /system/lib with the one from stock rom
Sent from my GT-I8160 using Tapatalk
1) backup tee folder
2) On build.prop change all GT-I8160L to GT-I8160 (without L)
3) all wipes factory/cache/dalvik
3) Install CM_Xversion
4) Whith roo explorer replace tee folder
Enjoy.
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
When to alter ROM
teddytsen said:
2) also can delete assert :/
4) you can just replace in zip before flashing (just sayin)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
KiwiCool60a said:
Am located in New Zealand, and hence using model i8160L, running stock JB ROM
Am trying to modify / install Maclaw CM KK ROM -- but am having problems
-- it "reads" the ROM and "immediately" (afaik) but aborts installation
-- NO ERROR MESSAGES come up for any indication as to why it's aborting
Am trying to do the following -- appreciate any feedback to correct procedure if I'm making eny errors
(i) omitting any and all references to L in 8160L string -- should I restrict it to any particular lines? -- using Build.Prop Editor
-- the Settings/About Device shows it as an 8160, rather than an 8160L after the Build.Prop changes, but the boot screen still shows it as the 8160L -- but at least I don't get the error message about trying to install ROM on wrong device
(ii) before attempting installation, downloading the latest ROM, unzipping the ROM using 7zip, deleting "tee" folder
-- and pasting tee folder from the stock JB ROM installed on my phone
(iii) re-zipping the ROM using 7zip -- I notice I get a different MD5 to that llsted on the download page
(iv) attempting to flash the modified ROM in Recovery mode, but it aborts
Don't know enough to know if install procedure tries to validate the "to be installed" ROM's MD5 and aborts since it's different from that on the download page
Don't know what purpose of tee folder is -- is it to connect to local carrier?
How about if I try to install "unmodified" ROM (in its unmodified form) and once it's installed, if it does (?), replace the tee folder at that later stage, to check for ability to connect to carrier?
Do I need to unlock the SIM card first --- as that's also something I haven't done
(naturally, I've backed up and able to restore to what I had before attempting the install)
Click to expand...
Click to collapse
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
When to alter ROM cont'd
teddytsen said:
md5 sum change probably because you uncompressed and re-compressed file.
no you dont have to unlock carrier.
use total commander and delete first 3 lines in updater-script.(all before mount.. bahblablah) and then compress it, then try.
btw it doesnt show any status errors?
Click to expand...
Click to collapse
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
KiwiCool60a said:
MANY MANY thanks for your very prompt reply, and further information
"status errors" -- as a result of ?? -- no status errors evident after rebooting with modfified Build.Prop
had lots of "fun" on my previous efforts with custom ROMs -- played with several on a Huawei G300 I had --
-- but, gee, this is an ongoing learning process -- now to learn about updater script !!!
(only learnt about Total Commander from your post - despite its high rating -- but note others have used other things for "text editing")
(but have discovered some TUTs on xda)
Reading more carefully through the posts I see it may be possible to flash the ROM, and then later, substitute the tee folder supplied in the Maclaw ROM with the stock JB one -- right?
I'll definitely learn more about updater-script, but I'll try to flash the ROM again without modifying the ROM === OK?
Click to expand...
Click to collapse
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Many thanks -- now for the "rest" and time for tee
teddytsen said:
-Dont care about ro.build.model. once assert is deleted you dont have to change it. And its not mandatory.
-I recommended total commander just because its the only root browser i have that shows the assert in 3 lines exactly. Unless es etc. You can also use other editors ^.^
-like when installation is aborted, it says status 7(or 0 etc)
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
Many thanks!! KK installed -- that was the "fascinating" thing -- no status errors on previous failed attempt at installation -- nothing
but now it's installed -- with GApps added, and now to "worry" about the rest of it all
unsurprisingly -- if tee does what I think it does -- but I can't find a TUT on that anywhere
-- so currently, I can't connect to my local carrier, so it's currently not a :"phone" as such
even more frustratingly, computer found phone when it was first plugged in, but now seems to have lost it!! time to reboot system
-- and, it's been a while since I used CM but I can't find extsdcard!!
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Permissions
teddytsen said:
Cm file manager?
Settings-general settings-access mode- root
Sent from my GT-I8160 using Tapatalk
Click to expand...
Click to collapse
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Lot easier than I thought -- and MANY thanks again
KiwiCool60a said:
sorry, not used to that one -- for that matter, I tend to stay away from things affecting the system I don't know
so I'm lost in permissions in different apps -- can't find "paste" in CM file, and can't find RW permissions in ES!!
But you're being exceptionally patient! thanks, heaps
Click to expand...
Click to collapse
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Repeated problems with Maclaw KK ROM
KiwiCool60a said:
Actually, it's a lot easier than I thought -- working phone, with KK installed -- without need to unlock carrier!!
Many thanks for the guidance, patience ....
and, of course, to the ROM developers
Click to expand...
Click to collapse
Many thanks for past help with intall procedure -- but have had repeated problems of late -- last installed ROM on March 9th -- could install several versions prior to that date, and use them successfully, but since then have been unable since I repeatedly get "Error searching for networks", and hence cannot connect to carrier, and hence unable to use phone as phone, though other functions seem to work OK, -- any ideas??
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]