Can anyone point me to a kernel that i can use with galaxy task 14 custom rom that has cifs/nfs built in?
Ive searched around and can only find ics kernels, and i can safely say that flashing one of those via cwm doesnt work for task14!
Thanks, zip prefered if anyone has a kernel to hand, makes cwm easier!
geekyhawkes said:
Can anyone point me to a kernel that i can use with galaxy task 14 custom rom that has cifs/nfs built in?
Ive searched around and can only find ics kernels, and i can safely say that flashing one of those via cwm doesnt work for task14!
Thanks, zip prefered if anyone has a kernel to hand, makes cwm easier!
Click to expand...
Click to collapse
This is the last HC kernel from pershoot with cifs support: http://droidbasement.com/db-blog/?p=2479
Select the right version and download the modules (in the same link, lib-2636.4_ux_hc32.tar.gz)
Thanks, from what i can see i need to flash the zip, extract the tar file then adb in and insmod?
Im happy with the flashing and tar extraction, butbwhats the insmod about?
geekyhawkes said:
Thanks, from what i can see i need to flash the zip, extract the tar file then adb in and insmod?
Im happy with the flashing and tar extraction, butbwhats the insmod about?
Click to expand...
Click to collapse
You don't need to do it with adb, use a terminal (command line) application like this one: Android Terminal Emulator, grant root (in the terminal execute su) permissions and run something like this (change the path to fit your case):
Code:
insmod /system/lib/modules/cifs.ko
You'll have to execute the command to mount your share too.
Or an easier way is using CifsManager, in the options you can set the path to your module and you can mount the share. I'm not sure if this one also works with NFS, it says so, but I never tried it.
Other way is with a script, using Script Manager or load the module at boot
Sweet, worked a treat thanks, once i worked out i needed to make /system readwrite and not just read onky.
Thanks alot for your help, i dont understand why cifs isnt just built in from scratch with android really, but sorted now. Just my phone to sort next!
Edit: how to i get my digicam pictres to show in the android gallery?
They are in te followinndirectory : /sdcard/nas/digi cam/
I can browse them in astro fine, but skifta and gallery dont show them / the directory.
Cheers
You're welcome.
Try using something like Rescan SD Card! or Rescan Media (personally, I use the "SD refresh toggle" widget from Elixir 2 - Widgets)
Oddly none of the as card refreshing tools updates the gallery app to.show the pics off my nas? It's mounted correctly I can see the files ok in astro.
What have I missed?
Questions go in the Q&A section
Related
Hi guys,
Couldn't find the answer to this anywhere but I noticed in the newer releases of busybox there's no 'zip' command anymore. I'm running busybox 1.19 on my Incredible.
I have been using this command to create different bootanimation.zip files from my phone but am wondering if there is an alternative command I can use from within Android. I've tried tar -cvzf but I believe tar archives/compresses the files differently and renaming the extensions to .zip does not work.
Any ideas besides using an actual PC to do what I want to do?
Thanks,
Zebdor
Sent from my Incredible using XDA App
There are apps out there such as AndroZip, that essentially creates zip files.
If you are doing this for an app, there are built in zip classes in Java.
java.util.zip.*;
Edit: Just realized you asked for it to be command line. I will keep looking!
Yeah, I used to use 'zip -0r ...' to zip up a folder but for some reason the busyboxes I've tried downloading don't come with the zip command anymore...
I'm looking through the BusyBox source...
Does it have to be .zip? I mean there are plenty of others to choose from such as tar, gz, bz.
I can't find anything on the website why it is left out.
Best of luck
travmanx said:
I'm looking through the BusyBox source...
Does it have to be .zip? I mean there are plenty of others to choose from such as tar, gz, bz.
I can't find anything on the website why it is left out.
Best of luck
Click to expand...
Click to collapse
I was thinking of using tar and gz but every tutorial I've read says Android requires the bootanimation to be in .zip format uncompressed. I even tried tarballing it as bootanimation.tar but it didn't work...
did anyone ever find an answer to this?
im currently trying to find a portable binary for just zip (or something like busybox that includes zip) because im trying to automate creation of a cwm zip ON an android device during the installation of another cwm zip
iXNyNe said:
did anyone ever find an answer to this?
im currently trying to find a portable binary for just zip (or something like busybox that includes zip) because im trying to automate creation of a cwm zip ON an android device during the installation of another cwm zip
Click to expand...
Click to collapse
This seems to work fine: https://code.google.com/p/zip-for-android/people/[email protected]
I thought I was crazy...
I have surely been missing the zip command too... I just got done downloading and about to reboot into recovery to install...
Zarchiver is a free app in the market that i use to.make boot animation zips and any other kind of zip on my Android device.
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
It's possible. In fact I mentioned this about a month ago to a developer.
I would like to see one that has a couple of options such as flashing recovery and flashing boot.img files.
You can easy push the flash_image binary to /system/bin and set the permission to 755. In fact my CWMFaux kernel does just that. Faux stopped using it because it doesn't always work.
In fact I made it so easy that all you need to do is push the boot.img to /system and reboot. Yet... no one uses it. In fact I suggested to a couple of rom developers to simply add the binary file to /system/bin so that you can at least run the command from terminal but they don't even want to do that. I like being able to update my recovery at anytime by entering "flash_image recovery /sdcard/recovery.img" and then just rebooting to recovery. You can easily do that for kernels too. But I suppose it's so much easier to carry a computer around.
Binary100100 said:
It's possible. In fact I mentioned this about a month ago to a developer.
I would like to see one that has a couple of options such as flashing recovery and flashing boot.img files.
You can easy push the flash_image binary to /system/bin and set the permission to 755. In fact my CWMFaux kernel does just that. Faux stopped using it because it doesn't always work.
In fact I made it so easy that all you need to do is push the boot.img to /system and reboot. Yet... no one uses it. In fact I suggested to a couple of rom developers to simply add the binary file to /system/bin so that you can at least run the command from terminal but they don't even want to do that. I like being able to update my recovery at anytime by entering "flash_image recovery /sdcard/recovery.img" and then just rebooting to recovery. You can easily do that for kernels too. But I suppose it's so much easier to carry a computer around.
Click to expand...
Click to collapse
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
Keep me posted will ya?
I believe that Faux and other developers would have to use the zImage kernel flashing technique to get it to work with his existing app but I'm sure he can simplify it to accept .img files and the .ko files in the /system/lib directory of a zip file. It actually should be very easy. It took me about ten mintues with testing included to create the script for my method. I just can't code for apps else it would be done by now.
DEFINITIONOFREAL said:
Im going to contact joeykrim and see if I can get him to add support in his app, and Ive been using your method since I got the phone (2 days ago) and started reading, but still a little hassle, and a big htc fail
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
I contacted pershoot, no answer lol!!!
Joeykrim is willing to support the Amaze, he just needs testers, this would be a great backup incase the new script failed to push the kernel. I'll keep everyone posted with updates
Sent from my HTC Amaze 4G using XDA App
I've been working with joeykrim getting his app setup for our device, it looks like it should work, hopefully, within the next couple of days we can get this working and released
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
I've been working with joeykrim getting his app setup for our device, it looks like it should work, hopefully, within the next couple of days we can get this working and released
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
That would be wonderful!
I'm tired of having to repeat myself.
flash_image boot /sdcard/boot.img
flash_image recovery /sdcard/recovery.img
Binary100100 said:
That would be wonderful!
I'm tired of having to repeat myself.
flash_image boot /sdcard/boot.img
flash_image recovery /sdcard/recovery.img
Click to expand...
Click to collapse
I just wish the devs would use your script, it would make things so much easier
Sent from my HTC Amaze 4G using XDA App
DEFINITIONOFREAL said:
I just wish the devs would use your script, it would make things so much easier
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Binary100100 said:
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Click to expand...
Click to collapse
could a script be written to automatically flash these while installing/flashing the custom rom? This would cut down atleast the step for flashing kernels for a lot of noobs!!
seansk said:
could a script be written to automatically flash these while installing/flashing the custom rom? This would cut down atleast the step for flashing kernels for a lot of noobs!!
Click to expand...
Click to collapse
Actually, yes! I did add it to the init.d script but since xboarder had removed the init.d scripts from his rom it doesn't work anymore. But you sure could. It was basically how I was setting up my CWMFaux kernels. However it didn't seem to work 100% of the time. Couldn't figure out why.
It basically worked like this...
Flashing the CWM custom kernel .zip via recovery.
copies boot.img to /system
copies init.d 06tweaks script to init.d folder.
copies and set permissions for flash_image binary and kernelupdate script to /system/bin directory.
You then boot your phone up which triggers the init.d script which commands the kernelupdate script to initiate. The kernel update script is simply using the flash_image binary command "flash_image boot /system/boot.img" and it automatically updates the kernel. Then the init.d script removes the boot.img file from the /system directory to keep it from flashing upon every boot.
I would like to change it to /sdcard directory but there's the problem that the sdcard doesn't get mounted until the very end. WAY after the system. Which is why I stored it there. The system gets mounted even before the data partition so I couldn't even store the file in data because the script would run even before the data partition could mount. Basically the script is initiated while your still looking at the boot animation. Pretty much when your softkey backlights and led light comes on it flashes the new kernel. It's a pretty neat workaround if I must say but unfortunately nowhere near perfect and not even close to having an s-off workaround.
Now if you don't mind the fact that it won't be initiated upon boot I could make it so that it will flash any file in a perspective folder on the sdcard.
example:
kernelupdate would update the kernel with any *boot*.img file located in a certain directory... say /sdcard/kernel
recoveryupdate would update the recovery with any *recovery*.img file located in a certain directory... say /sdcard/recovery
The problem:
Some people would want to collect their kernels and recoveries and store them in those directories. That would NOT be possible since using the command "flash_image recovery /sdcard/*recovery*.img would flash any img file with the word "recovery" in it. So if there's more than one it would error out and not flash anything because of the conflict. Same principal with the kernel only MOST kernels are simply named "boot.img" where-as almost all recovery files have a unique name since they are all already custom.
Binary100100 said:
Actually, yes! I did add it to the init.d script but since xboarder had removed the init.d scripts from his rom it doesn't work anymore. But you sure could. It was basically how I was setting up my CWMFaux kernels. However it didn't seem to work 100% of the time. Couldn't figure out why.
It basically worked like this...
Flashing the CWM custom kernel .zip via recovery.
copies boot.img to /system
copies init.d 06tweaks script to init.d folder.
copies and set permissions for flash_image binary and kernelupdate script to /system/bin directory.
You then boot your phone up which triggers the init.d script which commands the kernelupdate script to initiate. The kernel update script is simply using the flash_image binary command "flash_image boot /system/boot.img" and it automatically updates the kernel. Then the init.d script removes the boot.img file from the /system directory to keep it from flashing upon every boot.
I would like to change it to /sdcard directory but there's the problem that the sdcard doesn't get mounted until the very end. WAY after the system. Which is why I stored it there. The system gets mounted even before the data partition so I couldn't even store the file in data because the script would run even before the data partition could mount. Basically the script is initiated while your still looking at the boot animation. Pretty much when your softkey backlights and led light comes on it flashes the new kernel. It's a pretty neat workaround if I must say but unfortunately nowhere near perfect and not even close to having an s-off workaround.
Now if you don't mind the fact that it won't be initiated upon boot I could make it so that it will flash any file in a perspective folder on the sdcard.
example:
kernelupdate would update the kernel with any *boot*.img file located in a certain directory... say /sdcard/kernel
recoveryupdate would update the recovery with any *recovery*.img file located in a certain directory... say /sdcard/recovery
The problem:
Some people would want to collect their kernels and recoveries and store them in those directories. That would NOT be possible since using the command "flash_image recovery /sdcard/*recovery*.img would flash any img file with the word "recovery" in it. So if there's more than one it would error out and not flash anything because of the conflict. Same principal with the kernel only MOST kernels are simply named "boot.img" where-as almost all recovery files have a unique name since they are all already custom.
Click to expand...
Click to collapse
quite a dilemma, I wonder if we could add pause to the script until everything is loaded on the first boot then after the pause the script flahes the recovery and more importantly the kernel!!! if this was possible we could keep the files in a separate place on the SD card.
Still nothing like S-off!!! Thanks HTC for being so dev friendly
seansk said:
quite a dilemma, I wonder if we could add pause to the script until everything is loaded on the first boot then after the pause the script flahes the recovery and more importantly the kernel!!! if this was possible we could keep the files in a separate place on the SD card.
Still nothing like S-off!!! Thanks HTC for being so dev friendly
Click to expand...
Click to collapse
I'm sure there's a way to add a delay timer of some sort. I'm just not that savvy. Easiest way would be through an app like Tasker.
DEFINITIONOFREAL said:
Would this be a possible solution to our kernel flashing problems, I know it works for the evo
Sent from my HTC Amaze 4G using XDA App
Click to expand...
Click to collapse
The short answer is yes!
I've setup the application to support the HTC Amaze 4G, but before I release it publically and officially, I want to have a few testers confirm everything is working properly for them.
Posted all the information in a new thread as this one seems to be covering a few different topics so I didn't want to "hijack".
http://forum.xda-developers.com/showthread.php?p=21574722
Thanks for the request and for reaching out to me DEFINITIONOFREAL.
Binary100100 said:
Once I see that they do I can work out something else like:
kernelupdate
recoveryupdate
kernelupdate would be
flash_image boot /sdcard/kernel/*boot*.img
recoveryupdate would be
flash_image recovery /sdcard/recovery/*recovery*.img
So that if you place ANY of the appropriate img file in the perspective folders on the sdcard partition it would flash the .img by just entering either of the two commands from adb shell or terminal.
But I'm not going to waste my time if the devs don't want to use it.
Click to expand...
Click to collapse
I think my application, Flash Image GUI, will be the best alternative, but of course I have a biased opinion!
Regarding alternatives, I think a simple sh script which takes an argument would make a nice wrapper. The argument would be location to the image file to flash. The script could either bundle the flash_image binary or take the location of it as another argument.
All depends on how the developers want to create some type of standard. Which is another great reason Flash Image GUI will work well as it contains everything required and doesn't rely on developers providing support in their ROM, only relys on developers following the standards for ROMs and kernel .zip files.
Also, in looking through some of the custom ROMs and kernel .zip files for this device, I notice one of the custom kernels does something similar to the suggestions above, it executes a file located in /system/etc/init.d on every boot which automatically flashes /system/boot.img file.
At first glance I was horrified to see this as this is a *major* security issue. If anybody were to place any type of file in /system/boot.img, either a rogue kernel or just a blank file, the script automatically flashed it on boot w/o any type of file verification or user notification!
Wanted to get that off my chest and discourage the use of *automatic* loading of any type of major file, such as kernel or recovery image, especially without at least file verification or user approval/notification.
I'll try and keep up with the thread and help contribute ideas to alternatives for anybody who wants to develop/implement! Great ideas in the thread and always enjoy reading community collaboration efforts, especially in resolution to manufacturer "adjustments" of standards.
ugh, sorry about the double post (too excited for being too early in the morning). if a moderator wants to combine my last two posts, please do. i dont have access to delete a post.
joeykrim said:
I think my application, Flash Image GUI, will be the best alternative, but of course I have a biased opinion!
Regarding alternatives, I think a simple sh script which takes an argument would make a nice wrapper. The argument would be location to the image file to flash. The script could either bundle the flash_image binary or take the location of it as another argument.
All depends on how the developers want to create some type of standard. Which is another great reason Flash Image GUI will work well as it contains everything required and doesn't rely on developers providing support in their ROM, only relys on developers following the standards for ROMs and kernel .zip files.
Also, in looking through some of the custom ROMs and kernel .zip files for this device, I notice one of the custom kernels does something similar to the suggestions above, it executes a file located in /system/etc/init.d on every boot which automatically flashes /system/boot.img file.
At first glance I was horrified to see this as this is a *major* security issue. If anybody were to place any type of file in /system/boot.img, either a rogue kernel or just a blank file, the script automatically flashed it on boot w/o any type of file verification or user notification!
Wanted to get that off my chest and discourage the use of *automatic* loading of any type of major file, such as kernel or recovery image, especially without at least file verification or user approval/notification.
I'll try and keep up with the thread and help contribute ideas to alternatives for anybody who wants to develop/implement! Great ideas in the thread and always enjoy reading community collaboration efforts, especially in resolution to manufacturer "adjustments" of standards.
ugh, sorry about the double post (too excited for being too early in the morning). if a moderator wants to combine my last two posts, please do. i dont have access to delete a post.
Click to expand...
Click to collapse
I look forward to tryin out your app.
It was basically what this thread was all about in the first place.
The clockwork method that you mentioned is the only workaround that I was able to come up with for custom kernels (like Faux123) because a kernel cannot be flashed through recovery without s-off. Really stupid. So I started thinking "How can we flash a boot.img file from recovery without the typical means?" Then came up with the solution to flash_image the boot.img file automatically IF the file is detected. But how to start a script automatically upon boot? init.d is the only way I could think of. Okay... so where to put the boot? I tried the sdcard but it failed to mount until it was way too late. So... data. Nope... still didn't mount in time. Cache? Well... how many developers will include a cache file into their roms? So the only other option was /system and it seemed convenient since /system mounts BEFORE the script can run (obviously) so that's why it is as it is. I also figured "If someone wants to flash a new kernel all they need to do is push the boot.img to /system and reboot." Must easier than using the EKF method (requiring PC access) and I don't know about you but I'm not around a computer 24/7.
Greetings everyone!
New *registered* user here! I've been frantically sifting through post after post on the forums all night hoping to get some help with an issue I am having on my Vibrant.
Goal:
Remove some bloatware ONLY, not looking to install any ROMs or modify the phone too much...just clean some annoying apps and icons off.
Phone Information:
Model SGH-T959
Firmware 2.2
Baseband T959UVKB5
Kernel 2.6.32.9
Build FROYO.UVKB5
I currently have the latest version of Java, Android SDK, and SuperOneClick installed.
Install directory of AndroidSDK:
C:\AndroidSDK
My method of failure:
Open SuperOneClick, Click "Root"
Start, Run, "CMD"
cd c:\AndroidSDK\tools
adb shell
mount -o rw,remount /dev/block/st19/system
This is where it fails and I run into an endless loop of it telling me the proper usage of the "mount" command. I thought I had it at one point but when I typed: rm /system/AmazonMp3.apk all it did was tell me that it was a read-only file and that it couldn't be deleted.
Can someone help lead me in the right direction of what I am doing wrong? I rooted and removed all bloatware about a year ago but I just did an upgrade through MiniKies to the latest version of firmware and I can't seem to remember the process I went through that long ago to get it done right.
I apologize for possibly asking a question that has been asked numerous times but I just couldn't seem to get the wording right to get any helpful results in the search of the forums. Thank you so much for the time in reading this and the future help if any can be provided. Have a great night!!!
It looks like you are in the wrong directory. Open a command prompt in
C:\AndroidSDK\platform-tools
Open the platform tools folder. Click on a blank space > hold down the shift key > hit right click > select open command window here. Then enter the commands:
adb devices "to check if your device is connected. also make sure usb debugging is enabled on your phone.
adb remount
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
If you want a list of all your /system/apps enter this command
cd /system/app
ls *.apk
This is much easier if you download rom toolbox from the market. All you do is go to /system/app and delete whatever bloatware you dont want.
BUT BE EXTREMELY CAREFUL WHEN DELETING SYSTEM APPS. ONLY DELETE WHAT YOU KNOW IS BLOATWARE OTHERWISE YOU WILL GET FC'S
good luck
Would I still need to follow the steps prior to that and use SuperOneClick to root the device or do I just skip that process and go straight to the cmd prompt?
Also, I followed a tutorial I found for installing the Android SDK that informed me to copy all the files from android-tools to the tools directory and use that instead but I don't know what the use in that is except for maybe a smaller directory name?
EDIT: I tried what you said with and with using SuperOneClick prior to the procedure and the cmd prompt displayed the following text:
*opened cmd promt in C:\AndroidSDK\tools (no files in platform-tools anymore)*
adb devices (it found my device connected)
adb remount (adb remount: no such file or directory exists)
The adb shell and su commands works fine BUT I still hit the endless loop of it trying to explain to me the "usage" of the mount command.
I will look into Rom toolbox as I'm trying to figure this out as well. Thank you.
I strongly recommend you download root explorer or some similar root browser app. Of course though your phone must be rooted. Just try rom toolbox. It has its own root browser within the app along with other useful features. This is probably the easiest way to uninstall the bloatware in your case since you are having issues with adb.
Sent from my Galaxy Nexus using XDA
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
CScrivener said:
Thank you!
Okay, I have the suggested "rom toolbox" downloaded from the market and I will try to use that but SuperOneClick does not root the phone deep enough for rom toolbox to see the phone as rooted so...will the "updated.zip" method work for this instead?
I haven't tried it before but I am willing to give it a go if you think it's the best method. If this is the method you recommend, would you happen to have a link to the most recent or atleast most trusted updated.zip rooting method?
Click to expand...
Click to collapse
You can try rooting your phone using this toolbox.
http://forum.xda-developers.com/showthread.php?t=954509
If that does not work for you i will try and find the link to the "one click root program" i use all the time.
Here is an excellent guide to root.
http://forum.xda-developers.com/showthread.php?t=849028
Sent from my Galaxy Nexus using XDA
Here is the program i use. Just remember to have usb debugging enabled on your phone. It really cant get any easier than this.
http://forum.xda-developers.com/showthread.php?t=739300
Sent from my Galaxy Nexus using XDA
So I downloaded the one click program you suggested and the program itself seems to bee pretty straight forward.
I connected phone to computer with debugging on. Opened program and hit one click root. It started doing it's thing...phone rebooted and went into recovery. I started to follow instructions up until I got to where it said install packages. When I clicked it, the phone said installation failed no such file our directory exists.
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Thank you so much for all the help so far, I feel like I'm so close but just not there yet. You have been an incredible help!
Sent from my SGH-T959 using XDA
CScrivener said:
The phone is looking for the updated.zip file but none exists in the one click folder. There is a root.zip and an unroot.zip...do I need to rename one of them to proceed???
Click to expand...
Click to collapse
The way (Stock) Recovery works is if you are not "Install from SD" then it will look for the file labeled Update.zip. So you can rename only the Root.zip to Update.zip and make sure that is the only thing on your internal SD labeled that or with .zip Put the unroot.zip in a folder for now. Then try again.
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
CScrivener said:
Alright, will give that a try when I get home. I thought I read that the program copied the update.zip file to the phone during it's process so I didn't want to do anything to work against that. I will rename one of the files, copy it to the phone and give the one click root another shot. Thank you!
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
There is no need to rename anything. The program does it all for you. Play close attention to the first screen (green one) if it says update.zip copied successfully it will then reboot your phone to stock recovery. Once you are in stock recovery all you do is click reinstall packages. Keep clicking reinstall packages even if it reboots the first time. To prove my point mount your phone to your pc and check to see if the update.zip is copied onto the root of your into storage. If not well copy the update.zip from the last guide i suggested from above.
Also check to see if the superuser app is installed on your phone. The program also installs that along with the update.zip. If you have superuser then go to the market download rom manager so you could download CWM.
Sent from my Galaxy Nexus using XDA
Alright, so I tried it again once I got home. Didn't work BUT I did see that update.zip was installed into my phone. The sig verification failed, which means I need to change recovery versions to the one that skips sig verification correct?
I'll go search the forums for that since I remember seeing that a little while ago but that is the correct path I need to take at this point in time am I right?
Thank you so much! Big big help!
You can pull the CWR from my signature. Same as before. Put it on your internal labeled update.zip, boot into recovery and and scroll down to Reinstall Packages. Hit it. It will cycle and probably come back to stock recovery. Hit Reinstall Packages again and the stock recovery will go from blue to green (CWR).
Side note, probably from there you will be able to install the Superuser update.zip. Just go to Install from SD card and find it and hit it. The reboot. Might not but the CWR instructions above shoudl work for you.
Well I changed the recovery version using the file from http://forum.xda-developers.com/showthread.php?t=833423 and then used the OneClickRoot and was able to get the update installed (I think). The phone booted up normally, I noticed that SU Permissions was installed so I figure I am rooted correct? WRONG. Rom toolbox says I am not. Is there another way to verify? Should I reinstall Rom toolbox incase it's just bugging out on me?
So I tried using Rom Manager too. Looks as tho SU is not installed correctly, will have to try again I guess.
Cannot install CWR, tried and the recovery text stays blue even after 14 times of reinstalling packages...
This phone will be sent flying across the room sometime tonight I'm guessing. About to erase the entire thing and try starting from scratch again. (Start from Eclair and work my way up maybe)
If you are willing to start from Eclair it would be soooo much easier that all this stuff.
Odin to stock, flash CWR from my signature, go from blue to green and then flash Fishman's Bionix and you are good to go. Simple and way easier than all this mess. Just download Fish's and put it on you SD card somewhere you'll remember. Once in green recovery just scroll to that ROM and flash it per OP.
We've just been trying to Root you since on your OP you said you didn't want to flash a custom ROM.
Well...I'm still trying to avoid flashing Roms (I've upgraded through MiniKies and that's it).
I've only been trying to root just to clean bloatware off but it seems that I must be lacking the technical skills to follow instrcutions properly....nothing is cooperating and even after following all steps nothing wants to work like it should.
Grrrr! One last try to get CWR working before I lose my mind and need to take a break/walk away for a bit.
Ok, so I'm currently back to stock Eclair (ew!!) and about to boot to recovery to install CWR. Wish me luck on that one....
Wooo, CWR up and running! Now I just have to work on a flash maybe or whatever steps were suggested next...I might try the ROM you suggested.
The ROM gets placed on external sdcard and installed from within CWR correct?
Do most ROMs remove bloatware and useless apps?
Yes and are pre-Rooted. Put the ROM.zip on either card. I have a folder that I use. Boot into recovery and get green recovery back. Go to install from SD, find the ROM and flash it per the OP instructions.
Bloat free, pre-Rooted and usually has Voodoo so you can get Voodoo Sound from the market and have a sonic ear-gasm.
Just wanted to say thanks for all the help! I installed the suggested ROM last night and I am very happy with the results thus far. It was alot easier than I thought it would be. Flashing a ROM was MUCH more simpler than the root only decision. Thank you again!
Hello all you Triple-Booters out there! I would like to introduce to you:
Convert2Dualboot-SD Tool
What is this you ask?
This is a little tool that I've put together that will convert any standard flashable roms for our Nook Color to be DualbootSD compatible. No more waiting on my lazy arse to update you guys!!! I used APK manager as a base for my script. I've written 3 different versions that will run on Linux, OSX and Android. All neccesary binaries are included with each version.
Click to expand...
Click to collapse
Can I use any kind of flashable zips?
Yes and no. You could use any standard flashable "rom" or "gapps" zips only.
Click to expand...
Click to collapse
How do I use it?
You drop a standard rom .zip into a "rom-to-modify" folder. Then execute a shell script that will give you an option to convert it for flashing to Primary or Alternate boot on the DualbootSD.
Click to expand...
Click to collapse
Can I use any CWM Recovery for flashing?
Absolutely not! Only use the CWM Recovery that was included with the DualbootSD.
Click to expand...
Click to collapse
Will you be updating this to add new features and stuff?
Not sure what features I can add, but you can always check the CHANGE LOG in post 3.
Click to expand...
Click to collapse
Can you give us step by step directions on how to use this?
Of course! See second post for more details.
Click to expand...
Click to collapse
***Disclaimer: Usual disclaimer applies here as well... you use this at your own risk, I am not responsible for anything that happens to any of your devices. You assume all responsibility when using this tool.***
Credits:
Daneshm90 for the APK Manager Script I used as a base
Pinako/Inportb/Jyio/Boss! - for his Android binaries
DizzyDen - for porting this over to DOS and his many ideas to get the script to where it's at
HacDan - for some bash guidance
If I forgot someone else, please notify me.
Convert2Dualboot-SD Tool-README
Convert2Dualboot-SD-Linux v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-Linux
4-At the termninal prompt execute the C2DSD script
Code:
$ sh convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Now browse to the C2DSD folder and you can find your DualbootSD modded rom file either in "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
9-Copy that file to the /sdcard partition of your DualbootSD
10-Boot to CWM Recovery that is included with the DualbootSD
11-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-OSX v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up terminal and cd into Convert2Dualboot-SD-OSX
4-At the termninal prompt execute the C2DSD script
Code:
$ ./convert*
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-Android v1.4
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-This will allow you to modify the zip files directly on your Nook
2-Extract the zip file you just downloaded to the root of your DualbootSD /sdcard partition.
3-The folder should be named c2dsd
4-In the c2dsd folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
5-Open up any Terminal Emulator and cd into the c2dsd folder which should be "/sdcard/c2dsd"
6-At the termninal prompt execute the C2DSD script
Code:
$ su
# sh convert*
7-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
8-Choose your option and wait while it does its thing.
9-Once it's finished you can exit the program by choosing "0"
10-Now you can choose to boot to CWM Recovery that is included with the DualbootSD
11-Choose "install zip from sdcard" and browse to either "Primary-Mod" or "Alternate-Mod" depending on your earlier selection.
12-Flash and enjoy!
Click to expand...
Click to collapse
------------------------------------------------------------------------------------------
Convert2Dualboot-SD-DOS v1.3
DOWNLOAD
*C2DSD=Convert2Dualboot-SD*
1-Extract the zip file you just downloaded anywhere on your system
2-In the C2DSD folder, there are 2 folders called "modify-for-pri" and "modify-for-alt". Copy your rom.zip and/or gapps.zip file into its respective folder. No need to rename the file as long as it has a .zip extension.
3-Open up command window and cd into Convert2Dualboot-SD-DOS or create a shortcut on your desktop
4-At the command prompt execute the C2DSD script
Code:
convert2dualboot-sd-dos
5-This will give you a menu where you can choose to modify the "rom" and/or "gapps" for either Primary or Alternate boot. It will also give you an option to clear out recently modded zips. Now with option to mod both ROM & GAPPS on the fly. Just place both files inside either "modify-for-pri" or "modify-for-alt" and choose the option to modify both from the menu.
6-Choose your option and wait while it does its thing.
7-Once it's finished you can exit the program by choosing "0"
8-Copy that file to the /sdcard partition of your DualbootSD
9-Boot to CWM Recovery that is included with the DualbootSD
10-Flash and enjoy!
Click to expand...
Click to collapse
And that's all she wrote... well he, being me.
If I've helped in anyway. Don't hesitate to hit the thanks button.
Change log:
v1.4 (6/8/2012)
-Fixed gapps being zipped with rom when converting rom & gapps together
-Added SDCacheMount to converted roms (see the SDCacheMount thread for more info)
-Fixed mkimage binary executing error for Linux version
-No DOS update yet.... DizzyDen?????
-Thanks goes to xda user "shumash" for the SDCacheMount addition into the script
v1.3a
-Mkimage error on Android Script fixed.
-Mkimage is dependent on 'libmusl.so' which I did not include and linked in the tools folder. I overlooked this tidbit because I had "BOTBREW" installed on my system so it never complained about linking to it.
v1.3
-I effed up on the script!
-RASTAVIPER kept asking me about issues with his gapps. Apparently the mod for Gapps Alt Boot had the wrong mount points inserted into the updater script. NOW I SEE IT!
-Also in the DOS version. Prep of ROM Alt Boot had the wrong mount points as well. Sorry guys.
-It's been fixed and uploaded. Please don't use v1.2 anymore. Thanks.
v1.2
-Changed up UI layout of script: Please re-read README from post 2 above for edited instructions.
-Edited script to speed up mod process (Thanks DizzyDen!)
-Added option to mod both "ROM & GAPPS" on the fly
-Android version now has a tool.img file. This makes modding quicker and safer.
-Added DOS version ported by DizzyDen! (Thank you sir!)
-Modding for EMMC dualboot version in the works???? (That's if you guys want it)
v1.1
-Added gapps option
-Cleaned up some scripting behaviors
v1.0
-Initial release
Well.. after some thought, it really didn't make sense to release this without an option to mod gapps for the DualbootSD. I mean what good is a rom without gapps?!
Convert2Dualboot-SD v1.1 is up if anyone wants to try.
Check post 3 for all changlogs.
Thanks,
Racks
Taking advantage of the opportunity to try something new, I made a dual-boot card for my sister-in-law.
This is cool. I actually haven't tested the card yet as I have my device flashed to internal and have modded the recovery some. I haven't backed up any of the changes I made (I know, I know) and don't want to have to do it again.
I may try updating the card now that you've included gapps, though. I hadn't made a bootable card since I first rooted this thing, and to be honest it was by accident even that time. So I was wondering how to get gapps, was thinking about setting an alt-recovery just for that.
But anyway, I hadn't looked at how to do the gapps yet, maybe it was easier than that. But this seems even easier.
Cool, man! I bet the dual/triple booters will love being able to make their own updates. The experience I had last night couldn't have been easier. My wife got me and her sister the Nooks at the same time, I am excited for her to see what I have been talking about the last six months.
I will be sure to try this once my NC gets here. Thanks!
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
Edit: That might just be the stupid __MACOSX hidden folder that osx likes to include Forgot to exclude that and the .gitignore file when zipping. Although they aren't detrimental to running the C2DSD Tool, you can choose to delete them if you wish.
Thanks,
Racks
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
Sounds like a plan... I just got in from work... and am off tomorrow.
DizzyDen said:
Thanks a lot Racks... great work... we'll get together and sort out the windows based version... can include it in your work here... or as another feature of the IMEI generator.
Click to expand...
Click to collapse
racks11479 said:
Awesome to hear! Was hoping you would jump in.
We'll hook up and get the Windows based version here as well as incorporate it into your IMEI generator.
Thanks!
Racks
Click to expand...
Click to collapse
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
racks11479 said:
DB zip? Sorry, but what are you referring to with that?
And could you also let me know which one you used? OSX, Linux, Android?
--SNIP--
Thanks,
Racks
Click to expand...
Click to collapse
Sorry for being vague. I meant the modded dualboot sd zip build. But I tried it again and it was fine, so let's say no more about it, eh?
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Anyone who tried the new modding option and that would like to share with us which CM9 rom (nightly) did he convert and is working fine after conversion?
spdsl said:
+1 from a meathead windows user here.
Sent from my NookColor racks tripple boot using Tapatalk 2
Click to expand...
Click to collapse
Was hoping to have something before I had to go to work this morning... didn't get it completed...
to keep as close as Racks' I will have a DOS batch file available sometime tonight...
True Windows GUI version will be available early in the week.
Keeping with Racks' desires... both will be open source and stored on his github... I use AutoIT for windows programming these things.
shumash said:
On a related note, since you're so motivated now, how about creating those separate cache1 and cache2 partitions so that we don't have to wait so long to boot between the two?
Click to expand...
Click to collapse
Racks, I just sent you a PM that might help with this issue.
shumash said:
Racks,
Works great but there's an odd 0 byte file in the DB zip called ^[email protected] Is that an artifact and can I just delete it?
Click to expand...
Click to collapse
UPDATE: I converted the latest Mirage build, and when I tried to flash it, Recovery complained that it wasn't a valid zip file. Checked it and the same weird file was in the converted flashable zip. When I ran the conversion a second time, all was good and it flashed as expected. I had deleted all the extraneous _MACOSX and .gitignore file stuff prior to running it the first time. BTW, the problem in the quoted post was when I converted an ICS build the first time, too. Racks, do you think that there is something that occurs the first time the script is run that is different on subsequent runs that might account for this?
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
RASTAVIPER said:
Just installed nightly 28.4 without Opengl and then gapps which appeared in the folder Primary Mod after conversion.
After that I cant get inside shop.I click to open it and it gets me back to main menu.
Any ideas?Reflashing of gapps didnt work.
Click to expand...
Click to collapse
Primary mod is for Primary boot. Default primary boot was CM7, so I'm assuming you formatted /system1 & /data1 before flashing?
Could you also unzip the contents of the converted gapps zip. And check the updater script. All /system variables should be /system1.
-Racks
I didn't format anything before flashing. I thought this as an upgrade, so after conversion I just proceed to flashing.
Finally, I flashed your own gapps that you have at your dualboot topic and now everything is back to normal.
Unfortunately, even after this upgrade, I still continue to deal with FC issues of mail, Facebook and of other random apps.I think there is some problem with my card and CM9, since CM7 runs perfect from emmc or from same mem card.
Unleashed from my Revolutionized Desire HD
I have a Zenithink Z282 C91 upgrade tablet on a custom rom and a custom kernel running 1.2ghz with a 2GB recovery data partition, is there a way to add cwm recovery to it?
have you downloaded the cwm app? if you have try installing from there?
or maybe check check around to see if cwm has been ported to your device yet, if its not you may have to do that yourself or ask one of the friendly devs round here
It doesn't work off the app. I can't seem to find that anyone has done it either. How hard is it to do yourself?
Ben36 said:
It doesn't work off the app. I can't seem to find that anyone has done it either. How hard is it to do yourself?
Click to expand...
Click to collapse
im not a dev so im not entirely sure, but i think you might be able to download a zip of cwm for a similar tablet and manually push the files to the right places in your root folders yourself?
so:
1) download a cwm zip for a similar tablet.
2) extract to a folder on your computer.
3)push the files using adb into the correct folders on the root of your device(or use an app such as es file explorer)
whitest0rm said:
im not a dev so im not entirely sure, but i think you might be able to download a zip of cwm for a similar tablet and manually push the files to the right places in your root folders yourself?
so:
1) download a cwm zip for a similar tablet.
2) extract to a folder on your computer.
3)push the files using adb into the correct folders on the root of your device(or use an app such as es file explorer)
Click to expand...
Click to collapse
I don't mean to offend, just inform..but you can't push files into a directory on the device to give it a custom recovery, there's actually a hidden 'recovery' partition that stores what basically amounts to a stripped down kernel, a basic menu and some utilities. In most cases, due to the type of storage and layout of the storage, the recovery has to be specifically made for the device in question, which usually requires that the manufacturer complies with GPL and gives out the kernel source code.
if two given devices are 'close enough' and use the same hardware and mapping, a custom recovery can be used on both devices, but that's not usually the case. your best bet is to check in the development forums for your given tablet to see if a recovery is available, or if someone is working on one.
I did a quick google search and didn't find any custom recoveries for the zenithink, but I really don't know much about the tablet to begin with so I may have searched incorrectly.