Related
Ok , I know there is thread about debian running fine on desire z but the tutorial there is highly unfriendly and there are some other stuff you need to do to your desire z. This is my first guide. The reason for posting in dev thread is because chroot and loop requires specific kernel support to power Ubuntu.
Just to explain certain terms here...
Kernel - the interface for android to access hardware. Note that andorid is stripped down version of ubuntu and it does not have loopdevice support
Loopdevice - Imagine virtual disk mount program such as Daemon tools. This requires specifically supported kernels such
Following tutorial will void your warrenty (root and s off) but you can change to warrenty friendly state of course XD Check out xda wiki for more info( study to know what you are doing there.)
There are plenty of guides to get su and busybox( allows android system to be able to utilise more advanced commands) so check out comprehensive guides for g2 and desirez in this wiki below is my version
-------------------------------------------------------------------------
If your phone is stock, do a lot of research before doing root and s off. cyanogenmod has good guide on wiki for you to s off and get permanet root. Just for you to know, s off is to disable security for us to flash new kernel with loopback support and root is well... needed for most of hacks in XDA XD
*note for noobs: this is tested with desire z but G2 should not have problems. just be careful of which device's gfree you are using to s off.
ENGINEERING HBOOT IS NOT REQUIRED FOR THIS AND IS NOT RECOMMENDED FOR YOU TO DO SO AS IT MAY BRICK YOUR PHONE YOU SHOULD NOT HAVE PROBLEMS FLASHING CUSTOM ROM/KERNEL WITHOUT IT (guides are confusing if custom roms require flashing hboot)
Preparation:
1. busybox (install titanium backup and under problems? you can install busybox in a easy way)
2. Recommended: Clockwork recovery(rom manager in market)
3.Root and S off
4.Optional : remove or move sd card installed apps to internal memory or else LOOPDEVICE may be occupied and you may not be able to mount ubuntu. Do this if you encounter error (caused by app2 sd) please note that recent builds in xda mount loop device as 255 to avoid this problem.
You might want to use adb if necessary
5. android terminal from market
6. 2gb free space in sdcard (certain builds use 4gb as storage image, which is limit for fat32 system)
---------Kernel preparation ---------------------------------
Flashing necessary kernel
1. Download suitable kernel with loop device support. I am using cyanogen -> virtuous-kernel-cyanogen kernel from ://files.virtuousrom.com/vision/kernels/
(add http infront) on Stock HTC Sense Rom
2. To flash this, from rom manager, boot into clockworkmod recovery and select zip file to flash. Nandroid backup is recommended beforehand
-------------------------------------------------------------------
Now your phone has loopback support to chroot into UBUNTU or DEBIAN
Well, this method is not native ubuntu but it works fine.
You can now follow any guide on XDA like G1,nexus 1etc on running linux in android. I recommend nexus 1 hacks .com for ubuntu setup or thread "Debian for Desire" for debian setup (note debian seems to have problem with vnc) there are a lot of newbie frendly guides to do this without partitioning your sd card.
What can you do with them? You can use full android terminal , use vim , open office, gcc or eclipse etc ... makes your HTC Vision true small computer with keyboard . Enjoy
Possible solution to errors you encounter while following chroot tutorial for other android devices:
-----------------trouble shoot--------------------------------
Errors:
/device/loop is busy etc.... chroot: cannot execute /bin/bash etc... shutting down ubnutu etc....
Solution: 1. Get loopback support by flashing above kernel i mentioned
if not 2. TYPE SU BEFORE YOU RUN BOOTSCRIPT ON ANDROID TERMINAL
or if they say the bootscript is not found then type sh ./*your boot script name*
if not 3. move sd apps to phone as i mentioned eariler
Other errors could be from not installing busybox.
Note that in some cases, busybox is included inside the custom rom so you dont need to install it.
Post names of kernels with ability to run ubuntu for others to know.I did not test all of them.
This is my first guide on xda and i hope this helped xda in constructive way...
Post script: I will try my best to maintain quality of the posts to be up to xda standard. Thank you for constructive feedbacks...
quick problem i noticed
I'm running post ota de-odexed and I installed virtuous-kernel_vision_advanced-v1.0.9.zip in attempts to get loopdevice but now my phone doesn't react to an touch... hahaha it's no biggie I can't fix, just wanted to state out a weird outcome I have never seen before
But hey! Your prep guide is much appreciated!
EDIT: All of the 1.0.9 kernels seem to break my touch :/
you need virtuous-cyanogen 1.3 not standard vituous kennel. it is under cyanogen. Since it is developed for cyanogen, it should be fine for wide range of roms including sense roms but yes, it is buggy. I am looking for better kennel now....
squarememory said:
Ok , I know there is thread about debian running fine on desire z but the tutorial there is highly unfriendly and there are some other stuff you need to do to your desire z. This is my first guide. The reason for posting in dev thread is because chroot and loop requires specific kennel support to power Ubuntu. Well, do not attempt this unless you can use computer well XD
Following tutorial will void your warrenty (root and s off) but you can change to warrenty friendly state of course XD Check out xda wiki for more info( study to know what you are doing there.)
-------------------------------------------------------------------------
If your phone is stock, do a lot of research before doing root and s off. cyanogenmod has good guide on wiki for you to s off and get permanet root. Just for you to know, s off is to disable security for us to flash new kennel with loopback support and root is well... needed for most of hacks in XDA XD
*note for noobs: this is tested with desire z but G2 should not have problems. just be careful of which device's gfree you are using to s off.
ENGINEERING HBOOT IS NOT REQUIRED FOR THIS AND IS NOT RECOMMENDED FOR YOU TO DO SO AS IT MAY BRICK YOUR PHONE YOU SHOULD NOT HAVE PROBLEMS FLASHING CUSTOM ROM/KENNEL WITHOUT IT (guides are confusing if custom roms require flashing hboot)
----------------------------------------------------------------
Preparation:
1. busybox (install titanium backup and under problems? you can install busybox in a easy way)
2. Recommended: Clockwork recovery(rom manager in market)
3.Root and S off
4.Optional : remove or move sd card installed apps to internal memory or else LOOPDEVICE may be occupied and you may not be able to mount ubuntu. Do this if you encounter error (caused by app2 sd)...
adb if you want to type things in cmd
5. android terminal from market
6. 2gb free space in sdcard
---------Kernel preparation (may not be needed in some custom roms)---------------------------------
Flashing necessary kernel
1. Download suitable kernel with loop device support. I am using cyanogen -> virtuous-kennel-cyanogen kennel from ://files.virtuousrom.com/vision/kernels/
(add http infront) on Stock HTC Sense Rom
2. To flash this, from rom manager, boot into clockworkmod recovery and select zip file to flash. Nandroid backup is recommended beforehand
-------------------------------------------------------------------
Now your phone has loopback support to chroot into UBUNTU or DEBIAN
You can now follow any guide on XDA like G1,nexus 1etc on running linux in android. I recommend nexus 1 hacks .com for ubuntu setup or thread "Debian for Desire" for debian setup (note debian seems to have problem with vnc)
What can you do with them? You can use full android terminal , use vim , open office, gcc or eclipse etc ... makes your HTC Vision true small computer with keyboard . Enjoy
Possible solution to errors you encounter while following chroot tutorial for other android devices:
-----------------trouble shoot--------------------------------
Errors:
/device/loop is busy etc.... chroot: cannot execute /bin/bash etc... shutting down ubnutu etc....
Solution: 1. Get loopback support by flashing above kennel i mentioned
if not 2. TYPE SU BEFORE YOU RUN BOOTSCRIPT ON ANDROID TERMINAL
or if they say the bootscript is not found then type sh ./*your boot script name*
if not 3. move sd apps to phone as i mentioned eariler
Other errors could be from not installing busybox.
Note that in some cases, busybox is included inside the custom rom so you dont need to install it.
Post names of kennels with ability to run ubuntu for others to know.I did not test all of them.
This is my first guide on xda and i hope this helped xda in constructive way...
Click to expand...
Click to collapse
it's KERNEL! not KENNEL!
teh5abiking said:
it's KERNEL! not KENNEL!
Click to expand...
Click to collapse
Really dude? That was the only time he mispelled it and you the spelling police make a lousey post as if he mispelled it everytime...get a life
Sent from my HTC Vision using XDA Premium App
Well thanks for spelling correction. English is not my primary language
Spastic909 said:
Really dude? That was the only time he mispelled it and you the spelling police make a lousey post as if he mispelled it everytime...get a life
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Tell it spastic tell it!
xsteven77x said:
Tell it spastic tell it!
Click to expand...
Click to collapse
I thought you were insulting him XD
I have installed ubuntu without a hitch, but how do i fix the incorrect key bindings?
im thinking of using the technique that uses vnc to access ubuntu on my desire z. i am running 2.3.3 (cyanogenmod-7.1.0) on it. now forgive me for asking this its nearly 1am and im exhausted so my brain is not working right. which version of the kernel am i best getting for this? im a novice at it all but i do want to make sure i do it properly and dont brick my phone.
traumatism said:
im thinking of using the technique that uses vnc to access ubuntu on my desire z. i am running 2.3.3 (cyanogenmod-7.0.0) on it. now forgive me for asking this its nearly 1am and im exhausted so my brain is not working right. which version of the kernel am i best getting for this? im a novice at it all but i do want to make sure i do it properly and dont brick my phone.
Click to expand...
Click to collapse
This is a thread about installing ubuntu on the phone, not accessing it from the phone.
tsubus said:
This is a thread about installing ubuntu on the phone, not accessing it from the phone.
Click to expand...
Click to collapse
*facepalms* yes i know that. i will be installing it along side android and using vnc to access it locally. its a method i wish to use but i need the kernel for installing ubuntu and want to know which one. i shoulda made it more clear really.
ive just tried flashing the latest kernel for cyanogen with 7.1 but it freezes at the HTC screen on boot. any assistance will be apreciated
I am posting to spread the word for the best scripts on any android device i have ever seen and proven to work on various android phones and tablets that i own! Especially the htc Desire!
Original Thread: http://forum.xda-developers.com/showthread.php?t=991276
by: Zeppelinrox
None of these scripts is my work and only speaking from profound experience! I cannot describe how amazingly these 3 scripts can change the phone completely! It is now Superfast, no lag! and 3G is instant!!
Only works for rooted phones!
Very simple, follow the steps and couple requirements in original thread.
I'm using InsertCoin_GB_Sense 2.1 v1.1.4 rom. This should work for any android device flawlessly with little risk!
My settings for V6 Supercharger script
In script manager make sure root privilege is on but not boot!
512HP Super UL Option 7
then SuperClean and ReStart Option 30
KAK RC3
In script manager make sure root privilege is on and also boot!
Followed and accepted the prompts
3G TurboCharger
In script manager make sure root privilege is on and also boot!
I used Experimental 1
I used the following releases:
V6 SuperCharger Update 9 RC5, 3G TurboCharger RC3, KAK RC3 and DHBC RC2
Download Page: http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
I was looking at this yesterday as its in mildwild. You really think its good?
Sent from my HTC Desire using Tapatalk
rootSU said:
I was looking at this yesterday as its in mildwild. You really think its good?
Sent from my HTC Desire using Tapatalk
Click to expand...
Click to collapse
It's good, this and titanium are the first 2 things I install on a new rom. Makes even sense 3.5 fly on our old desire.
From my HTC Desire AIO
What settings do you use?
I've installed it but to be honest, I already had some tweaks in place that this gives. I haven't noticed any improvements really.
Good for everyone else though. Looks well written.
Alright. After having installed this on my 2.3.3 Desire some 3 hours ago, i do see a noticeable improvement, especially in the way the launcher acts. It's much more fluid, even after a wake-up (when i used to get a little lag). I have configured the Supercharger just as the OP said and i have also installed the "KAK" module. I haven't installed any other module than these two (as i find no need for them).
How to install, for dummies:
1) Download "V6_SuperCharger_for_Android-Update9_RC5.2.sh.pdf" and rename it to "V6_SuperCharger_for_Android-Update9_RC5.2.sh.txt". Download "KickAssKernelizer_Tweaks_Installer_Update_3_RC3.1.sh.txt". Copy both files to the root of your SD card;
2) Go to the Market and download "Script Manager";
3) Open Script Manager and select "V6_SuperCharger_for_Android-Update9_RC5.2.sh.txt". After the "pop-up" opens, click on the SuperUser icon and then click "Run" (no need to modify any other settings). This gives Script Manager root acces, which it needs for the script to be able to modify key system files;
4) Follow the on-screen instructions (that's a no brainer);
5) Do the same for "KickAssKernelizer_Tweaks_Installer_Update_3_RC3.1.sh.txt"*.
*Note - i haven't fiddled with the I/O tweaks, as the script said they're sort of experimental.
Advice: it's best to have an init.d enabled ROM, as this allows the Supercharger and KAK to run their scripts automatically during start-up. This cuts the need to use Script Manager to run them at boot, thus making life easier.
I've been using it for the longest time that I can't remember how my phone works when I don't have this running. CM7 is fast enough as it is... so there really isn't much to push in terms of speed but yeah you'll probably notice some slight improvements here and there.
I wonder what you would think after having it unsupercharged and unkernelized for a couple of days... lol
zeppelinrox said:
I wonder what you would think after having it unsupercharged and unkernelized for a couple of days... lol
Click to expand...
Click to collapse
Maybe when I'm bored I'll uninstall it. I'm happy with your scripts and it's not giving me any negative performance issues to make me remove it.
after 2nd boot... my BravoC feels faster than before, especially when i try to look apps list after booting. superb !!!
would really appreciate a little help with installing this mod.
I read this on the ics thread -
You have to put the file as is it is in the sd card and then run the terminal
emulator and type:
su [enter]
sh \sdcard\[the name of the file] and again enter and then follow the guide.
the name of my file is -V6_SuperCharger_for_Android-Update9_RC8.2.sh
ive tried this many times , not working
do i change file extention by renaming ?
rraaka said:
emulator and type:
su [enter]
sh \sdcard\[the name of the file] and again enter and then follow the guide.
the name of my file is -V6_SuperCharger_for_Android-Update9_RC8.2.sh
Click to expand...
Click to collapse
did you try with this command?
$ su
# sh /sdcard/V6_SuperCharger_for_Android-Update9_RC8.2.sh
make sure the script file is in root directory of your sdcard and busybox already installed.
Thank you so much agis, it worked !
im using insertcoin 114 right now.
my phone booted fine
but im not sure i chose the right options !
it gave some warning about the busybox,.....but proceeded
build or local ? scrolling 1, 2 or 3 ? and many options
id like a guide to optimum preferences
but thanks anyway !! the literature is fun
obviously Im doing something wrong in the options.. my phone freezes from time to time and i have to pull the battery
when we have to choose buil or local...which is right ?
thnx
rraaka said:
obviously Im doing something wrong in the options.. my phone freezes from time to time and i have to pull the battery
when we have to choose buil or local...which is right ?
thnx
Click to expand...
Click to collapse
i choose build.prop and the script is running fine. but i use gingerbread, not ics.
maybe you can consult with the script creator about your problem. the link is in my signature.
This is an all new way to root and install bootmenu (2nd init) with only one click!
Just running runme.bat you will have a Bravo ready to use new roms in less than a minute.
Instructions:
1. Download: http://www.mediafire.com/?yfgvds9a1w8sbds
2. Extract files whenever you want.
3. Enable USB debugging (menu > Settings > Applications > Development) and connect your phone to the PC.
4. Run runme.bat, in folder Root+Boot-AIO.
5. Press Enter when script ask you to do it and READY!
Note: remenber to install motorola drivers first.
Reserved for instructions in spanish and other language!
Thanks. Finally find another one click option.
Sent from my HTC Sensation using Tapatalk 2
Tested, worked like a charm!
Thank you! :good:
Wow
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Junkyardjames87 said:
Just one word, wow, works like a charm. Now we can install a custom rom with like 4 steps now. Your 1 click would be step one for sure!
Good job and lots of props man!
Click to expand...
Click to collapse
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
skeevy420 said:
I've looked into it. While there are a few options to install roms from the pc, some of the commands are known to hang on completion, which means you can't really script them safely (you could add in some kill and restart commands, but you'd have to put like 2-5 min buffers on them to make sure it was done).
I've found that the quickest way to install roms is to use TWRP in the Defy Forums. It allows you to select multiple zips at a time to flash at once. I haven't used clockwork touch recovery yet.
I'll look into it a little more, cause typing something like "./rom_install.sh /path/to/rom.zip -gbgapps" to install a rom and gb gapps would be easy. If I can find a way to execute edify scripts (the ones used to install roms) from adb then this can be done. I can only make and test linux scripts since I no longer have windows, but Josuearisty can port it to windows shell script. I formatted my old windows drive to use my android compile drive .
Click to expand...
Click to collapse
Im not using TWRP either Touch Clockworkmod, both of them are not working as they should sometimes.
I supose that a fully working Touch Clockworkmod would restore an old backup made with our actual Clockworkmod recovery, but does not.
In the case of TWRP, works fine for some time but later it seems to get tired and when you make a backup, it says its complete inmediatly but it is still creating backup files.
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
josuearisty said:
It would be great to install roms with just hitting Enter coming from froyo. Do you think that just making some changes to the script, is it possible to install a rom the pc?
Click to expand...
Click to collapse
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
skeevy420 said:
I'm sure its possible somehow, I've just never looked too deep into doing it. What ways I have found either used commands that would hang and require you to quit after 2 mins of activity and start the 2nd command which hangs the same thing -- not safe enough to script. The other ways were for broke\no sdcard and involved copying the rom to /data and then installing as normal.
What I think needs to be done is set up a script that copies the rom & gapps to the sdcard and executes their edify scripts. We need to figure out what command recovery uses to execute the script\install roms then incorporate it into an install script. You'd still have to reboot to bootmenu and enable adb, but that's all (unless we find a way to reboot and have adb already enabled (not good for all the time use, security concerns - it'd be possible to get around the bootmenu pin if adb was enabled on power up).
Click to expand...
Click to collapse
Well, look at the rom manager, watch how it does it. I think that looking into adb commands we can make a script works like rom manager.
When you select the rom, rom manager lets you wipe data & cache and also install gapps. The rom manager goes to recovery and inmediatly do all steps it self, you can also backup your actual rom.
Try it, download it from market and try it, I see your roms there too.
Some windows commands are:
Adb reboot recovery = reboot into recovery mode
Adb push FILE = copy files to whatever place into out phones. Example to copy a rom.zip to sdcard
Adb push rom.zip /sdcard/rom.zip
Those are windows commands, dont know if they could work on linux. If my pc wasnt broke I would be making some tests!
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
This will root and install a custom recovery.
Excellent tool, recommended! :good:
josuearisty said:
This will root and install a custom recovery.
Excellent tool, recommended! :good:
Click to expand...
Click to collapse
Great. Thank you. I'm rooting a friend's phone. He just wants something more reliable than stock. Would you say the CM7 is stable and reliable or should I put CM10 on it?
obsanity said:
Does this install a custom recovery? And if not how do I install one? Will a goo manager from the play store install one?
Sent from my Nexus 4
Click to expand...
Click to collapse
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
josuearisty said:
CM7 is more stable now, I have installed an official cm7 and then a patch for it.
Give me some minutes to upload it!
Click to expand...
Click to collapse
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
obsanity said:
Which one should I use? Also, what is the SBF for Motorola Bravo? Sorry about the questions in this thread, I'm not familiar with this phone.
Click to expand...
Click to collapse
Use cm7. Very fast and stable with no random hiccups, rare force-closes. The SBF is the Motorola Bravo "factory ROM". To install it, you can use RSDlite or do it in linux, both of those tuts are found in the bravo general section. You probably won't have to use the SBF unless you brick your phone, which is a possibility, but flashing the sbf will unbrick it 99% of the time.
Current ROM: CM7.2 Euroskank Cherry Picks | Bravo port
I think I have a problem. The sim I put in to this phone is asking to log in with moto blur and nothing I try is working. So I can't switch the debug mode on. I even tried the bypass suggested by someone but fastboot is not preinstalled on this phone. All I get is the bootloader or stock recovery.
I also tied resetting the password but after I go thru it it just says there is no phone on this moto blur account.
Any help would be appreciated.
Edit:
I got it. I factory reset the phone and then was able to use the bypass motoblur ****.
Sent from my Nexus 4
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
shvelo said:
Ruined my device,now it won't even boot.
How do I fix it? factory reset doesn't help
Click to expand...
Click to collapse
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
skeevy420 said:
Post a little more info.
What did you do?
Can you access custom, stock, or bootloader recovery?
Does it still charge?
And did you factory reset from Custom recovery or Stock recovery? Custom only wipes all data where Stock actually formats the partitions.
The easy way and a common issue we're having now.
Unless this is one of those CM10 ext4 issues, just flash the sbf and you should be good to go.
If you downgraded from CM10 and you were using ext4 /data and /cache, reinstall CM10, format back to ext3, then flash whatever you want.
Click to expand...
Click to collapse
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
josuearisty said:
What is that issue with cm10 ext4? Is that very dangerous for us?
I have been sometime out of the forum and I have lost some things!
Click to expand...
Click to collapse
The CM10 ext4 issue is when you flash a CM10 custom kernel rom and select format /data & /cache to ext4 in the bootmenu. Only custom kernels can use the ext4 file system, so what happens is you format them as ext4, install CM9, and it doesn't load because it can't mount /data and /cache to write them because they're on an unsupported file system. The only things you can do are reinstalling CM10 and formatting back to ext4 of flash the sbf in extreme cases. Its not dangerous at all, just very annoying if you forget to format back to ext3 .
Do someone know how to update cwm v6 from v5? B/c I want to see what CM10 look like and mostly of the time, it said installation fail or something...
How did you install v5? I would assume you can repeat the process to flash v6 in its place.
you can use rom manager
i2nice said:
Do someone know how to update cwm v6 from v5? B/c I want to see what CM10 look like and mostly of the time, it said installation fail or something...
Click to expand...
Click to collapse
i had the same problem other day
cm-10-*.* = CyanogenMod 10 Rom
gapps-jb-20120726-signed = All the google apps not included in the rom
recovery-clockwork-6.0.1.2-d2att = Cwm
Install
1. Install ClockworkMod Recovery for "d2att".
to do this install "Android Terminal Emulator" from the market "https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en&rdid=jackpal.androidterm&rdot=1"
Put the file in the sd directory of your phone, not on the card, and rename it "recovery.img" from recovery-clockwork-6.0.1.2-d2att.img
Open Terminal Emulator and run the following commands one after another:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18
then boot to cwm and install cm10-*.*
then install gapps-jb (google apps)
Mange to got it works! Made to v6 from v5. Thanks guys for the tip! Also, @smelenchuk, I believe that I found the v5 one from team epic.
Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}
Dude360 said:
Hi
I have some weird questions some problems that Im trying to figure out, hoping someone can help or point me in right direction.
Im not new to 'Android' but this are beyond my scope.
Ok, so, the WFS. Got it unlocked, S-Off, rooted etc thats all fine.
Now, the basis of my troubles come with the zips and updater-binary. It seems that every zip I have can be flashed on any device Ive tried (from N4 to a OUYA to a HUDL to a Nook Simple Touch etc) all except the ruddy WFS.
I either get a status error or a binary fail.
I used to have to grab a updater-binary from a current ROM zip and replace it in every zip I wanted to flash which just got annoying. Even then it will only be certain recoveries that will flash them.
I only use my WFS as a remote for XBMC and not as a 'phone' but like to keep all my devices as current as technically possible.
Im trying to find out what is the cause of this and how to make it so that all my zips work with all my devices off the bat.
Maybe not your usual questions but either way I could do with extending my knowledge a little and getting this sorted
{ffs posted in General by mistake, apologies}
Click to expand...
Click to collapse
What is it you are flashing exactly? And which recovery are you using? Could be a problem with the recovery you use
I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.
Dude360 said:
I have many zips which do many things but they all use the same binary..
eg,
I have a zip which i use to remove .ogg from the /system/media/audio folder and extracts my own set of sounds. Or
I have a zip which has a game apk and its relevant obb files which extract to save me downloading them again.
etc
These have all been flashed on a large variety of devices without a hitch.
They will work on WFS using an update-binary from a WFS ROM zip but not with the one I use for the rest.
I have tried these on every recovery from CWM 5x to the very latest TWRP compiled recently by Oliver for the CM11 builds.
I suspect that it is something to do with the recovery as I also cant get other things to work.
eg.
For ROMCleaner we use a custom busybox binary which does some work in /tmp and our romcleaner binary which does the brunt of the work.
busybox will error (but for life of me cant remember what it says), while the RC binary will 'exit status 4'
Ive been playing with the WFS version of ROMCleaner for a long time now and am determined to get it working properly.
This is where my knowledge ends really, it could be something to do with the binary, with ARM6, the kernal used in the recovery or an evil gremlin determined to make me rake down and cry.
Just looking for big shove in the right direction.
Click to expand...
Click to collapse
TWRP will not work with older update-binary. Could you upload an example zip which does not flash ?
This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!
Dude360 said:
This is a test zip im playing with, all it does is extract busybox to /tmp, mount the three partition, make a folder on each partition then unmount.
Doesnt even get that far. Heres the part from recovery log, used CWM 6.0.5.3 from Oliver for this one.
Code:
-- Installing: /storage/sdcard0/test.zip
I:Cannot load volume /misc.
Finding update package...
I:Update location: /storage/sdcard0/test.zip
Opening update package...
Installing update...
[B]I:Using legacy property environment for update-binary...
I:Legacy property environment initialized.
I:Legacy property environment disabled.[/B]
E:Error in /storage/sdcard0/test.zip
(Status 0)
Installation aborted.
I:Cannot load volume /misc.
I:Can't partition non-vfat: /storage/sdcard0 (vfat)
Assuming the bold part you meant about older binaries, just wondering why its only the WFS that cant do it and how to get round it.
Appreciate the time guys!
Click to expand...
Click to collapse
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.
aWFSuser said:
A status 0 would refer to a update-binary or updater-script failure. CWM now falls back to a legacy mode when an older binary is encountered. So I would recommend to use a newer binary. Or you could try an older CWM. TWRP does not at all works with the older binaries since 2.3. What recovery are you using in your other phones?
Click to expand...
Click to collapse
That error would make sense then, reverting to an older binary.
From memory, Ive used these binaries myself on:
Desire
CWM 5x, 6x
EXT4 Recovery All versions
Desire HD:
CWM 5x, 6x
EXT4 Recovery All versions
Nexus 4:
CWM 5x (I think it was)
TWRP 2.x to latest
Nexus 7:
TWRP 2.x to latest
Samsung S2
Aman Ra I think its called
Transformer 101
CWM 5x (I think)
Nook Simple Touch:
CWM 5x
OUYA:
CWM 5x
Tesco HUDL
CWM 5x
Several Cheap Chinese Tabs with CWM 5x
And as far as I know they've been used on the rest of the ROMCleaner devices as well, but have no idea about the recoveries as I was on hiatus for some of them.
Sensation
Incredible S
One X
One S
EVO 4G LTE
HTC One (m7)
HTC One (m8)
GNex
TF201
Galaxy S3
Galaxy Note II
Galaxy S4
I remember we did a LOT of testing with updater binaries to find one that was compatible with as many devices as possible but at the time none of us had access to a WFS hence why we were never able to check with them.
We we quite surprised that this one worked with everything we tested and tbh I cant even remember where it came from and Its still running on everything we throw at it!
aWFSuser said:
BTW what rom are you using ? Because at least in CM there is no /storage/sdcard , its just /sdcard . I don't know about stock though.
Click to expand...
Click to collapse
I was using PA at the time, same error with CM11 though.
At the end of the day, the binary can be worked around. The romcleaner binary not working is (child status 4 error) cant!
Im beginning to think its definitely a recovery incompatibility, maybe the way it has to be compiled to run on ARM6 or maybe just particular to the WFS.
The romcleaner binary hasnt changed either and is running on the above devices as well.