Database Develop

[HOW-TO] apps2sd on n1 cyanmod

I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
As usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
EDIT:When updating to a new CM rom you WILL encounter a boot loop, simply run the steps below AGAIN during the loop cycle and then reboot the phone and it should work.
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj

Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?

heroskyy said:
Attempted this, and I've never once tried doing apps2sd. I dl'ed the files to the root of my SD card after partitioning the SD card to ext2. After this was done, I went to my terminal emulator, but all I get from the commands are "adb: not found"
What am I doing wrong?
Click to expand...
Click to collapse
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.

nonmindo said:
I thought since the cm5b4 thread is getting hard to navigate through that i would pull some helpful info out of it and make it in a seperate thread
I TAKE NO CREDIT FOR THE INFO BELOW, jerbarton should get credit for the procedure
AS usual I'm not responsible for any problems you may encounter or broken phone, i also cant confirm if this works on any other rom's but cyans and there is no gurantee it will always work but here you go
ALWAYS NANDROID!!
you will need to have an ext2 partition before this will work, i believe you can make one with the "partition" option in recovery
Code:
adb remount
adb push 04apps2sd /system/etc/init.d/
adb push e2fsck /system/xbin
adb shell
chmod 755 /system/xbin/e2fsck
chmod 755 /system/etc/init.d/04apps2sd
mkdir /system/sd
Downloads:
e2fsck: http://www.mediafire.com/?tzwwjyz2t2r
04apps2sd: http://www.mediafire.com/?mjjntmtmjmj
Click to expand...
Click to collapse
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.

kamasi36 said:
You have to get the android sdk kit on your computer and type in those commands from tools. Make sure those files are placed in your tools folder so it can find them(adb). Also need to hold down shift and right key to open up command in folder.
Click to expand...
Click to collapse
awesome! thank you! Ive always been confused about that

heroskyy said:
awesome! thank you! Ive always been confused about that
Click to expand...
Click to collapse
Ha. me too man. You have to learn fast on here. They expect us to know all this stuff coming in the gate. Just holla back if you need some more help. I'm a noob too but managed to figure it out.
http://forum.xda-developers.com/showthread.php?t=532719
This might help you get started. make sure you get everything updated because this is kind of dated.

kamasi36 said:
Thanks for putting this up but your crediting wrong person. First and foremost Cyanogen(his script pulled from rom) Second, dhanj was the first to post the script on here and the other guy added to it( the one your giving credit too.) Go back and read original post.
Click to expand...
Click to collapse
Yeah cyanogen (especially) and dhanj should be credited more than me. I didn't really do anything but add on how I got it working for me.
One thing to mention, if cyanogen doesn't implement this officially in his ROM (and for most people it's probably not needed) you'll have to redo this procedure each time you flash/update so I'd suggest keeping the 2 files saved.

@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3

dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
In any case, I was also hesitant on starting a new thread about this because of the apps2sd, need or not to need discussion that's been going on. Anyway, I'm glad you did post this and glad that there are others asides from myself(kamasi, jerbarton, t0pgun & dscottjr81 that I know of!) who chose to get this up and running on their nexus one.
As for who get's credit, I certainly cannot take any credit for this because all I did was share information. The real credit goes to cyanogen and the great devs we have here on xda that made our toys even more enjoyable that it was stock.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
Thanks dnanj. Just upgraded to ext. 3. apps2sd b4 now.

You betcha....as always, just sharing information whenever I can.

am i suppose to get a conformation in shell if the commands worked?

Ohal_yeah said:
am i suppose to get a conformation in shell if the commands worked?
Click to expand...
Click to collapse
When the commands complete, you should be brought back to the prompt where the shell awaits the next command.

I apologize for not looking deeper into who deserves credit here, thanks for those of you that do know!! I was simply just trying to make it easier to get the information to people that might want it...
as for the debate of needing a2sd or not, i was out of space right from the get-go because of all the apps i had on my mt3g...so to me i definitely need it out of the 1gb partition i made on my sd card i have .82 free now lol...

completed all steps but everything still saves to internal memory

JustinLoe said:
completed all steps but everything still saves to internal memory
Click to expand...
Click to collapse
a small glitch probably when you run the last command before adb reboot, it fails to create the directory as it exists, probably change the name to solve it, it happened to me once

dnanj said:
@nonmindo...thanks for posting this, I've been meaning to put something together but had a handful of things going on.
Edit:
Regarding the second(ext) partition that's created when you partition your sd card using RA-nexus-v1.5.3 recovery, there isn't a menu option to upgrade your partition to ext3, unlike other versions of Amon_Ra's custom recovery for the HTC Dream: G1.
Regardless, of this you can always go back into the recovery, hook up your phone to your pc, open up command prompt and type in the following commands:
Code:
adb shell
sdparted -ufs ext3
Click to expand...
Click to collapse
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA

jakontil said:
hi, what does the code has anything to do with app2sd? anyone cares to shed some lights to a newcomer?
TIA
Click to expand...
Click to collapse
ext3 is essentially a ext2 file system with journaling.
Click Here to read about ext3 and it's benefits over an ext2 fs. As to why ext2 over ext3 for apps2sd, since journaling improves reliability of the fs, that makes it more ideal than ext2.

it works great thanks!

hi dnanj
thanks for the link

sorry but im stuck here
C:\android-sdk-windows\tools>adb remount
remount succeeded
C:\android-sdk-windows\tools>adb push 04apps2sd /system/etc/init.d/
failed to copy '04apps2sd' to '/system/etc/init.d/': Is a directory
C:\android-sdk-windows\tools>
why does cmd show me this error can you help me out please..very much appreciated

HELP! cant do nandroid recovery via ADB 'unaffys not found in path ?'

Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated

Quick update, I have Cyanogen 6.0.0 working on the phone now..
But i'd still like to be able to restore!

jamin100 said:
Would really appreciate some help here guys...
basically i have a new SLCD nexus one with Ramons 1.8.01 recover image.
I tried uploading a few roms but none of them worked..
so I'm trying to restore one of two nandroid backups i made before i started messing..
on the phone if i go into recovery and select nandroid restore then i get an error telling me to run nandroid-mobile.sh via ADB.
So, i set up adb, follow a guide (here) and end up with an error saying
error: unyaffs not found in path
does anyone know how i can get that backup working???
I've attached a copy of my cmd window..
Any help would be gratefully appreciated
Click to expand...
Click to collapse
I would suggest trying to type the directory instead of using default. When the restore prompts you to either type the directory or hit enter... instead of hitting enter type:
/sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
See if it gives you the same error.
NOTE: That IS case sensitive.

Thanks for your reply, unfortunately it does give the same error, I have 3 nandroid backups but cant restore any of them which is worrying incase anything happens to the phone!
Please help

Try this... while in the shell... type the following:
Code:
ls -l /sdcard/nandroid/HT08BP800418/BCDS-20100911-2252
It should bring up a list of 5 files. Go ahead and attach a screen if you can if you are getting a list of files. If not let me know what error you get.

Thanks for your help,
here's the screen shot

Nobody encountered this problem?

Ok... sorry had you look in the wrong place. I thought it was looking in the directory with the image in it for what it needed. I just looked at the nandroid code. Turns out... it looks for some executables that are required for the script to run. It doesn't have to do with your image and I think your images are probably fine.
I need you to run 2 more commands so I can see where the problem is. First run:
Code:
env
Next run:
Code:
which unyaffs
The "env" command should show your enviroment variables. What we are looking for is for /system/bin to be in your "PATH" variable. It should be because it checks for another executable first "flash_image" and it is not coming up with an error. The second file it is checking for is "unyaffs". Next you need to check and make sure unyaffs is actually in your /system/bin folder. It is probably not... and would explain the error you are getting.
I guess my first question is... is this happening on all ROMs you have tried (or have you only gotten one up and running)? If it is there may have been a problem when you flashed it. Even though it is possible that you could copy it to the /system/bin I would suggest not doing this. The reason is because if that one file is missing... there may be other files missing that should be there from when you flashed your ROM. These missing files... if there are any... could cause problems later. It might be best just to reflash whatever ROM you are using. I would suggest CM6 (not nighties) and then moving to some other ROM once you get a "known good" to work with.

Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...

jamin100 said:
Hey GoblinLord,
Thanks for your help on this, really appreciate it..
OK, well i've ran the two commands that you said and have attached the screenshot with the output. I've tried going to /system/bin but get permission denied errors through adb.
Although it looks like the PATH is actually /sbin rather than /system/bin ???
As for the roms..
I'm currently using CM6 (the stable version) as this was the only one that I could manage to get to work. As this is a SLCD nexus i dont think there are many roms that have the right drivers for the screen. Its does work fine though.. The nandroid restore is the only part of the phone that i cannot get working....
Again thanks for the help...
Click to expand...
Click to collapse
Hmmm... the permission denied is normal. That is because it is a folder and not an executable. You should be able to do:
Code:
ls -l /system/bin
This will list what is in your /system/bin directory. As for your path being different... that seems a bit strange. I am doing the commands from a terminal on my device... once I get back home today I will do it through the ADB shell and see what I get. The "which" command will only look in the folders in your "PATH" variable for the executable. If /system/bin is not in there I am not sure how it is passing the part where it looks for "flash_image". In my sbin folder I only have the ADB daemon (adbd) executable. What you could do is manually add the /system/bin to your PATH variable while in the shell... that may work. You can try the following:
Code:
PATH=$PATH:/system/bin
Run that before running your restore command. That should manually place the directory you need into your PATH environment variable. I will do a little testing with ADB once I get home and update this if I get to before you try it.

Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App

jamin100 said:
Thanks for the reply....
I won't be able to try this until Wednesday as I have left the USB cable at work ....
I will try it Wednesday and let you know...
Thanks
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I checked my environment variables via ADB. Mine did show the /system/bin in my PATH variable. Seeing as this is a shell being run on your device... I would still venture to say that something may have went wrong when you flashed your ROM originally. That or something you installed changed it for some crazy reason (and shouldn't have). Either way, I still think it would be best to flash again... possibly to a different version. I know you would have had to get a modified version of CM6 so... if you don't mind me asking where did you get your copy?
EDIT: Correction... I am getting the same path variable as you when in recovery mode. I am not quite sure why this is... the guide I found for using nandroid restore through ADB doesn't seem to run into this issue. It might be some kind of issue related to just Amon_Ra recovery. This would mean that Amon_Ra Recovery just didn't add it to the PATH variable... which I guess is rather odd... but whatever. Just try manually adding it to the PATH variable as mentioned above and then run the restore. It should work then.
EDIT 2: I did a bit of researching on that error you are getting when you try and restore in recovery. Reference:
http://forum.xda-developers.com/showthread.php?t=621940
Various people point to things that may cause this error. Is your phone charged? Do you have plenty of space on your SD card?

[How To] Recover from a soft brick

A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now

Thanks! Extremely happy you are deving for this phone

What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.

uskr said:
What's the best way to backup my stock partitions before I keep playing with those files?
Titan Backup works for that?
Or just a tar cf /mnt/sdcard/systembackup.tar /system , works?
Thanks in advance.
Click to expand...
Click to collapse
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.

Thanks! I am messing around with the APKs and scripts to get the webtop to work without the dock. So I wanted to make sure I was covered.

designgears said:
I would just use the tar solution, much easier to deal with.
You can also use ADB, adb pull /system system
Also, the retail dump I did matched my phone dump bit for bit, as long as you have that you should be fine.
Click to expand...
Click to collapse
I already did both adb pull of system and tar, but how did you do the retail dump?

lpsi2000 said:
I already did both adb pull of system and tar, but how did you do the retail dump?
Click to expand...
Click to collapse
tar dump as root of system

One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.

uskr said:
One last question.
Once I deodex my /system/app, should I just do a adb push app /system/app and then rm /system/app/*.odex ?
I am used to use the update.zip trick on the captivate. But I am not sure how to proceed on this phone.
Click to expand...
Click to collapse
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;

designgears said:
push apps, then push framework, reboot, then delete all the odex files, reboot
from system do something like; find . -name "*.odex" -exec rm {} \;
Click to expand...
Click to collapse
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.

lpsi2000 said:
Unrelated to this, I could sware yesterday I got to the recovery screen where I was able to wipe stuff and also be able to use update.zip. Although I did not use and update files but saw the option there. Today I am looking everywhere but the recovery screen does not come up with the options. I only see exclamation point and the droid. May be I am going nuts but can anyone confirm this.
Click to expand...
Click to collapse
tap at the bottom right of the screen right above the search button

designgears said:
tap at the bottom right of the screen right above the search button
Click to expand...
Click to collapse
ahha, thank you. Now I know I am going crazy. I used it yesterday to wipe when the system was unstable on me after playing around with the framework. I am must have stumble on that by accident. I am wondering if this documented yet somewhere around here.
Also too bad we cannot get root from there yet.

Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.

realawill said:
Well thank you for this. So when it boots to run, does it do a sys check to verify files are the same size or what? Anyway went to my local AT&T store and they swapped it out for me.
Click to expand...
Click to collapse
No, I just made a bad edit and it was FC hell

IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.

designgears said:
No, I just made a bad edit and it was FC hell
Click to expand...
Click to collapse
Crazy....mine just would not reboot. But good to know that there is a way to recover. Love the phone but hate Motorola. Wish that it was easy as the Cappy.

Cool stuff. I may snatch the framework off the phone in stock form and make a batch package for this so folks can easily just double click to restore their framework and system app folder.
Good work DG...

I never get past that initial... Starting RSD protocol support screen. Is that fast boot? If so I'm a retard...
EDIT: I need the face palm sticky. It's not Volume UP...it's Volume Down. Reading comprehension for the loss...

azy8000 said:
IT DOES NOT WORK WITH ME
I have been trying this trick for many times. The device restart and SuperOneClick hanging without any result.
Click to expand...
Click to collapse
I have done this several times now, it works

I soft bricked my Atrix earlier this morning, and used this to recover. The time limit is a serious pain!
I ended up needing to separate /system into 5 separate pushes of 30MB each in order to get them done in time.
Oddly, after restoring everything, the phone is no longer associated with my motoblur account, and I can't add it.
Also, I think there my be some files in /system that are unaccounted for by the filesystem, as there is 70MB more than what is present.
Edit:
Restoring the system fixed both above problems.

[HowTo] ClockWorkMod Recovery

Thanks to Trekfan422991 for cluing me in on the Optimus 3D recovery.
Working:
Nandroid
ADB (after special driver install, need to tweak recovery for it to work with normal drivers)
Mounting USB to computer
Flashing zip files
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
I am in the process of making a recovery specifically for our device, it is mostly done and will be posted here when it is ready!
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
If you don't understand something in that list, DO A SEARCH AND LEARN, don't clutter the thread with crap!
Lets get started!
Lets start by getting the recovery.img file on the phone. Open up a cmd prompt and type:
Code:
adb push recovery.img /data
The rest of this will be done on the phone shell. In the cmd prompt type:
Code:
adb shell
We will need to have su access, In the cmd prompt type:
(If you haven't allowed shell su in SuperUser now would be a good time to accept the root request on the phone.)
Code:
su
Now we are going to backup your current recovery to your sdcard. In the cmd prompt type:
(make sure your sdcard is not mounted to your computer)
Code:
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
After that is done we are going to flash ClockWorkMod Recovery! In the cmd prompt type:
Code:
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
Congrats! You now have ClockWorkMod Recovery! In the cmd prompt type:
(each line is single command)
Code:
rm /data/recovery.img
reboot
How to enable ADB access: (only if it's not working already)
Download and install: (unzip and install the 2 exe files)
http://www.mediafire.com/?j5m1plnvzb8r0zc
While booted into ClockWorkMod Recovery, go into your device manager, you should see an "LGE Android Composite Device" with a yellow triangle on it.
right click on it, update driver software...
select browse my computer for driver software
select let me pick from a list of device drivers on my computer
click the "Have Disk" button
click the "browse" button
browse to;
for 64bit:
C:\Program Files (x86)\LG Electronics\LG Android Driver\64BitADB
for 32bit:
C:\Program Files\LG Electronics\LG Android Driver
and select lgandadb.inf
click "ok"
From that list select "Android Sooner Single ADB Interface"
click "next"
click "yes" on the popup
Click to expand...
Click to collapse

Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose. Good thing I am having issues with permissions with this didn't notice the SD Card Mounting issue till just now. That I can't deal with atm.

malickie said:
Awesome Great Work. Did you figure out the Bootloader? Or is there even one should more be the question I suppose.
Click to expand...
Click to collapse
I found a few modes, but no drivers yet so I don't know what they are. Even if we break stuff the kernel and recovery are separate, so technically we should always be albe to get back into recovery to fix stuff.

thankyou DG for getting this started..
so now with my clockworkmod i just made a backup of stock rom... if i say change the framework and I get boot loop.. will this clockwork mod be able to restore the original rom without any problems???

tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...

Trekfan422991 said:
tiny problem... might just be missing something... but after i made my backup and i choose reboot system now... it just goes back to recovery... how do i boot up my phone!!!
sorry if it is obvious... im super tired...
Click to expand...
Click to collapse
I got mixed up as to what partition to flash, you just flashed a recovery image over the kernel... its ok tho.
follow my instructions to the su part, then do this.
// this will restore the kernel
dd if=/sdcard/mmcblk0p5.backup of=/dev/block/mmcblk0p5 bs=4096
// this will backup recovery
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6.backup bs=4096
// this will flash cwm
dd if=/data/recovery.img of=/dev/block/mmcblk0p6 bs=4096
OP is fixed!
edit--
and you have no adb access, this is going to get interesting!

haha... i shoulda noticed
____

LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha

Trekfan422991 said:
LET THIS BE A LESSON FOR ALL OF YOU!!!!
THIS IS WHY YOU ALWAYS ALWAYS MAKE BACKUPS!!!!!!
NEVER SKIP THE BACKUP STEP!!!! haha
Click to expand...
Click to collapse
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.

47r0n1n said:
LOL! For sure that is why I always say, " Save early, save often, save to multiple locations!" haha.
Click to expand...
Click to collapse
sorry just side note:
how you liking your thrill compared to the evo 3d???

designgears said:
What you are going to need:
ADB (and know how to use it, don't ask in here)
Rooted Phone (again, that will not be covered, don't ask in here)
Optimus 3D recovery image [Download]
Click to expand...
Click to collapse
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?

Komodo Rogue said:
Thanks so much to DG & Trekfan, I've been looking everywhere for CWM!
I cannot find the download link to the recovery - in the quote above from the OP, where it says download, is that supposed to be a download link? I don't know if there's a typo or if I'm just missing something, but the "download" word doesn't link to anything for me. Instead, I thought I'd try searching for it in the optimus 3d forums, but search is down too Does anyone have a link?
Click to expand...
Click to collapse
I took it down for now, working on some issues.

Woohoo, got Trekfan422991 all fixed!

its true... i tested out my framework mod and it works great!!! look sway better then stock!!!

designgears said:
I took it down for now, working on some issues.
Click to expand...
Click to collapse
Ah, gotcha. I thought I was going crazy Thanks!

Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!

designgears said:
Dangerous:
Fix Permissions (caused lots of crazy issues, fix by wiping data if you use it)
Sdparted (the sdcards are mount incorrectly, this will probably destroy your device)
Click to expand...
Click to collapse
After CWM is installed and working on our device, would it be safe to fix permission in "ROM Manager," or does that just fix permissions through whichever recovery is currently installed?
I'm guessing someone here knows how ROM manager works in this regard, but if not, I'd be happy to be a guinea pig... after all, I can make/restore backups now! : )
gtg465x said:
Let's rom this baby dg . I assume you also bought this with plans to possibly exchange it when the AT&T Galaxy S II comes out? I'm very impressed by the performance and build quality so far. The main thing it needs is a better theme... yikes!
Click to expand...
Click to collapse
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be

Komodo Rogue said:
Sorry for being OT but I must agree: if designgears made a Thrill ROM that's Cognition-esque then I'd consider keeping my Thrill, but considering he already has a ROM for the GSII, I imagine he's going to get the AT&T Galaxy S II? Side note, you know you've really earned some serious nerd-cred when other nerds (who you don't even know) speculate what your next cell is going to be
Click to expand...
Click to collapse
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.

Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?

gtg465x said:
Not waiting on dg here. Think you missed the "let's" part. Working on a Thrill ROM as we speak. Just got the Thrill about an hour ago and I already dumped the system image, de-odexed it, created an updater-script, added root and busybox, removed bloat, and updated a few apps. Time to start theming, modding framework, and tweaking.
Click to expand...
Click to collapse
Oh, good to hear! Man I really have to sit down and try to learn some more technical stuff sometime, because ROM creation, and not even just the theming aspects, is so appealing to me.
Maybe you can create a thread placeholder and describe what you've done so far? We're really getting OT, sorry all.
timbrendelaz said:
Im also working on a ROM but if we cannot flash zips with CWM then how am I supposed to flash the ROM? Are you going to flash it with Heimdall or something?
Click to expand...
Click to collapse
Oh, I thought you could flash zips through adb after doing the fix? Or no? (((edit: wait, no, I was thinking about pushing .apks through ADB, not flashing .zip files))) Hopefully this is something DG's new recovery might address. If no to both, could you distribute ROMs via nandroid backup files of a fresh ROM installation? It would be incredibly inefficient, but it would work, right?

cwm touch

So iam running bo 2.0.1 with cwm 5.5.0.4. Tried to update to cwm 6 touch by replacing cwm image in pretty much all the aio's.. it'll either say it pushed and still reboot into old cwm or I'll get permission denied on /data/local/temp/sh and mmcblk14 even after giving them all read write and execute permission. Can someone help me get this on my revo? Maybe a guide to do it with adb? It would be much appreciated..... sorry if this is posted in wrong section... I wasn't sure where it would be seen by the dev 's who can help

All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!

slimzim said:
All I had to do was use this tool:
http://forum.xda-developers.com/showthread.php?t=1630821
After you unzip that file, download the CWM 6.0.0.0 img file and rename it cwmrecovery.img and replace the one in /files. Then run the Run Me.bat and select option 2 - it says Root and CWM 5.5.0.4, but since you replaced the img file it'll push the one you want. Make sure your phone is in Internet Connection more and turn on USB Debugging. I hope that works!
Click to expand...
Click to collapse
The same exact way I've done it. Numerous times with no success. It said it pushed but reboot back into 5.5.0.4

Anyone else have this problem? How can I achieve this with adb or file explorer... the method posted just isn't pushing the image...

To do it from within the phone... (Insert the usual disclaimers here about messing your phone up here. It's all you from here on out)
You can open up the .bat batch file of one of the rooting tools that have CWM install scripting.
Copy the commands they perform in preparation for the procedure. Remove adb shell and push from the commands as you will be doing this from inside the phone, not via adb. I think you might have to remove some open/close quotation marks too, unnecessary from the terminal prompt.
Rename the new CWM file to match the command prompt change the command to match the new CWM filename.
Move that file to the expected location (/local/tmp if I recall correctly).
Use app Terminal Emulator to create a terminal windows and type su and Press enter. That will get superuser access.
Then, issue the commands you took note of from the batch file.
Reboot to Recovery to test if successful.
I used this basic process to get CWM on after rooting stock ZV9 a few weeks ago. Combing through a couple different batch scripts, I wanted to make sure I wasn't going to bork my phone. The adb remount command doesn't seem to work after rooting for some reason. That seems to be the cause of adb failure to update CWM.
If you get into trouble, I can't help you much there as I'm not that advanced. Good luck.
Anyone else with tips please chime in and help the chap :beer:
Sent from my VS910 4G using Tapatalk 2

Ill try it out. Thanks for the advice

Didnt work.. iam hoping that resetting back to stock and using that image from the start will work

Weird. I was expecting to hear good news since that's how I got CWM onto my phone. Good job trying!
Sent from my Transformer Prime TF201 using Tapatalk 2