Database Develop

switchrom problem

if follwed all the steps in :http://forum.xda-developers.com/showthread.php?t=541183. (i got to download switchrom.txt as switchrom.sh and i downloaded it to root of my sd card AND to a folder System>sd) when i do the command:
sh /system/sd/switchrom.sh -s <name>(i put drizzy-hero) and it says sh: can't open ' /system/sd/switchrom.sh' any help? im running drizzy's champion v2 cyan. recovery1.4

francoghini said:
if follwed all the steps in :http://forum.xda-developers.com/showthread.php?t=541183. (i got to download switchrom.txt as switchrom.sh and i downloaded it to root of my sd card AND to a folder System>sd) when i do the command:
sh /system/sd/switchrom.sh -s <name>(i put drizzy-hero) and it says sh: can't open ' /system/sd/switchrom.sh' any help? im running drizzy's champion v2 cyan. recovery1.4
Click to expand...
Click to collapse
So I assume that you are going into Recovery and then you enter "mount system/sd" and you then enter the "sh system/sd/switchrom.sh -s drizzy-hero" then hit enter?
You have to remember to mount the sd.
"mount system/sd" to access the system/sd directory
"mount sdcard" to access the sdcard
You can't access any files without doing that first.

ohhh thank you i will try again

doesnt work same error

francoghini said:
...(i got to download switchrom.txt as switchrom.sh and i downloaded it to root of my sd card AND to a folder System>sd) ...
Click to expand...
Click to collapse
how did you copy it to a folder system/sd? its important because i think you may have copied it to the wrong folder.
Code:
mount system/sd
mount sdcard
cp /sdcard/switchrom.txt /system/sd/switchrom.sh
this should be done in the console in recovery. if you do it in the terminal emulator you will need su first.

nvm its not working im running the commands correctly from the folder system/sd/ but it says storing nandroid backupumount can't umount /sdcard: Device or resource busy

anybody have any ideas? if you need me to ill post the .log

Step by Step
francoghini said:
anybody have any ideas? if you need me to ill post the .log
Click to expand...
Click to collapse
To Bookmark
Perform a nandroid backup from Recovery 1.4
Go to Console (ALT+X)
enter "mount system/sd"
enter "sh system/sd/switchrom.sh -s ROMNAME"
It should now read "Storing ROM ROMNAME, proceed? (y/n)"
enter "y"
It should then start saying "Storing app data..." followed by "Storing nandroid backup..."
During this time it is compressing the app, app-private, app_s (if applicable), and dalvik-cache in a tar file which is then stored in /sdcard/switchrom/ROMNAME/ directory.
After it is all completed it should read "Done bookmarking the ROM named ROMNAME."
Do NOT do a nandroid restore as it will revert to the latest nandroid backup. If you wish to do a restore use the switchrom script instead..
To Restore
Reboot into recovery
Go to Console (Alt+X)
enter "mount system/sd"
enter "sh system/sd/switchrom.sh -r"
It should now read a list of roms that you have backed up. Enter the number indicating the desired ROM to restore.
It should now read "Restoring ROM ROMNAME, proceed? (y/n)
enter "y"
It should then read "Cleaning up system/sd ..." This is deleting the app, app-private, app_s, dalvik-cache directories from your sdcard.
It then should read "Restoring ROMNAME app data in /system/sd ..."
Following next should be "Restoring nandroid backup..."
Things to keep in mind.
Always make sure you have enough battery remaining to do a backup/restore.
Always make sure you have enough space on your sdcard.
Always keep at least ONE nandroid backup in your nandroid folder should the switchrom script fail.
The script COPIES the files that are backed up in the nandroid directory to the switchrom script. If you don't have a large sdcard this may cause you to lose space fairly quickly.
To delete a stored rom enter "mount system/sd" then "sh system/sd/switchrom.sh -d" then the number of your ROM that you wish to delete.
Always keep an archived copy of your backups on your PC in case your sdcard fails at some point. A good habit would be backing up the Switchrom directory at least once a week.
Also make sure you have sufficiant battery life remaining. If you use an older switchrom script and you get a unable to umount /sdcard message this is normal.

i checked the switchrom directory and saw it had a the file in it then i checked the restore thing see if it was set up in the recovery console and it is=] i guess i was using an older version . i downloaded the attachment that was on the post though. wait no i checked the nandroid folder and its empty=[.
Going to try to clean up sdcard and try again
UPDATE: i cleaned it up same thing, in the middle of storing nandroid backup... it has the same error and tells me to check out the .log

francoghini said:
i checked the switchrom directory and saw it had a the file in it then i checked the restore thing see if it was set up in the recovery console and it is=] i guess i was using an older version . i downloaded the attachment that was on the post though. wait no i checked the nandroid folder and its empty=[.
Going to try to clean up sdcard and try again
UPDATE: i cleaned it up same thing, in the middle of storing nandroid backup... it has the same error and tells me to check out the .log
Click to expand...
Click to collapse
Post the Nandroid.log file in a text format.

how do i check the log? i did it before but i forgot ik it has to do with the adb

i even flashed amon ra's recovery and switchrom still gives me that error how do i check the log?

how do you use switch rom from RA recovery
I'm confused as to what commands to type for RA recovery image with switchrom built in .having same problem as the other guy.
The way you use it on RA recovery 1. 2. 3 is drop down to console by turning phone off. then holding home key and end call key to boot in recovery ,go to console and type "switchrom" now type
/sbin/switchrom ( command) then enter
Commands. -r restore
-s store
-d delete

[Q] I can't boot into recovery!

I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?

top_bunk said:
I rooted using UniversalAndRoot, which worked according to the app. Installed ROM Manager and flashed ClockworkMod Recovery.
This is where I stumble. I've tried selecting Reboot into Recovery, Install from SD, powering up with Vol Down pressed and selecting Recovery. All three boot as far as the X, flash a bit of white at the bottom of the screen then the phone turns off.
Waiting for a minute/pressing buttons or pulling the battery lets me boot back up fine, but I still can't boot into Recovery.
I've tried choosing install AltRecovery and old versions of Clockwork but they both behave the same way.
Any advice guys? Is it because I rooted with UniAndRoot?
Click to expand...
Click to collapse
You probably have SLCD screen. Then you have to use Amon_RA 1.8.0.1 recovery which is only one (as far as i know) intended for SLCD screens.

Ah okay. Is there an easy way for me to flash that? Not really comfortable with the SDK approach...
Thanks for the fast reply btw

If you don't have unlocked bootloader you have to use flash_image binary to flash new recovery because amon_ra 1.8.0.1 recovery don't show up in rom manager.
Download it from here http://cyanogen-files.carneeki.net/flash_image.zip. Put it in root of sdcard as well as 1.8.0.1 img file and in phone terminal type
1) cd /sdcard
2) flash_image recovery 1.8.0.1.img (replace with name of img file)

houmles said:
2) flash_image recovery 1.8.0.1.img (replace with name of img file)
Click to expand...
Click to collapse
I'm getting flash_image: not found
I've double checked the file name is correct

Did you unpack the zip file? There is only one file named exactly "flash_image" so you should not getting not found error if you have that file in root of sdcard and you are at /sdcard in terminal.
Send me output of "ls -la" command from /sdcard.

----rwxr-x system sdcard_rw 17638414 2010-09-10 20:20 gapps-hdpi-20100817-signed.zip
----rwxr-x system sdcard_rw 70864056 2010-09-10 20:22 update-cm-6.0.0-N1-signed.zip
----rwxr-x system sdcard_rw 11818685 2010-09-10 21:05 FRF50-radio-4_06_00_12_7.zip
----rwxr-x system sdcard_rw 4145152 2010-09-10 23:10 recovery.img
----rwxr-x system sdcard_rw 26172 2009-10-03 18:07 flash_image

Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>

Jack_R1 said:
Try ./flash_image instead of just flash_image.
One more thing: type this as the first command when you enter the Terminal:
su
Then type:
cd /sdcard
./flash_image recovery <insert_recovery_img_name_here>
Click to expand...
Click to collapse
./flash_image: permission denied

top_bunk said:
./flash_image: permission denied
Click to expand...
Click to collapse
Weird. Try:
1) su
2) cd /sdcard
3) chmod +x flash_image
4) ./flash_image recovery file.img

Well, that's because SD card isn't a good place to put flash_image. Permissions inherited from FAT32 are awkward and aren't changeable. But there's a way around it.
Do the following sequence: run Terminal, enter the following commands:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>

houmles said:
3) chmod +x flash_image
Click to expand...
Click to collapse
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.

Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
It didn't work...
Jack_R1 said:
su
cd /sdcard
cp flash_image /data/local/tmp
chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image <insert_recovery_img_name_here>
Click to expand...
Click to collapse
cp: not found

Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.

Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
I just thought of the same thing
Installing Astro now (it's a new phone no apps!)

Jack_R1 said:
Won't work for 2 reasons:
1) In Android, chmod seems not to recognize letters for permissions.
2) On SD card formatted with FAT32, the mount assigns default permissions for all files, and they can't be changed - since the file system doesn't support it.
Click to expand...
Click to collapse
ah, didn't know that
Jack_R1 said:
Have any file explorer installed? Astro / EStrongs / whatever?
Copy the file manually in file explorer, and skip the "cp ......" instruction.
Click to expand...
Click to collapse
As Jack wrote, you can only copy the file manually with some file explorer.

houmles said:
As Jack wrote, you can only copy the file manually with some file explorer.
Click to expand...
Click to collapse
It won't let me copy it... I've tried Astro and ES.

Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.

If you have adb connection you can try this:
unpack zip I sent you and recovery.img to root of c:\ for example .. then:
1) adb push c:\flash_image /data/flash_image
2) adb push c:\recovery.img /data/recovery.img
3) adb shell
4) chmod 755 /data/flash_image
5) /data/flash_image recovery /data/recovery.img

Jack_R1 said:
Lots of complications...
Install Busybox from the Market. Then you'll have "cp" working.
If it still won't work, try "busybox cp" instead.
Click to expand...
Click to collapse
Lots
...but it's done! Thanks a lot for the help guys
I've gotta be up in a few hours so I don't have time to install a ROM and faff about, but hopefully it will be all good from here on in.
Cheers again!!

[Q] FRG83D Update Problems

I have a rooted (rage) N1 that I loaded the G2 Launcher2.apk on to. Doing this caused the N1 to fail the update when it tried to apply FRG83D.
Stupidly, I decided that deleting the /system/app/launcher2.apk file was the right idea. And then rebooted.
Now the phone hangs on the boot animation. Attempting to apply with NO launcher2.apk results in the same error.
I have ADB installed, and I can adb shell into the phone and su. I have the old, original N1 launcher backed up on my SD card, but I can't figure out how to:
1) Mount the sdcard while ADB shell'd in from just the boot animation screen so that I can browse the card
2) Move the launcher2.apk backup file into the /system/app directory without getting a "Cross-device link" error when I use mv.
Can someone provide me with the exact commands to get the /sdcard/launcher2 backup/launcher2.apk file on to /system/app while ADB'd in only from the boot animation?
Thanks so much, I'm digging through the forums in the mean time, but it's tricky to track down exactly what to do.

I appear to have fixed everything. I wasn't able to access the SD card through ADB, but I *was* able to mount it using the:
Code:
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
method.
From there, I copied my backup to my desktop, and I found I was able to ADB push to just the /data/local/tmp directory. Don't know if I could've gone anywhere else, but that worked.
From there, I was about to:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
to mount/make writable the /system/app directory,
and then:
Code:
cat /data/local/tmp/launcher2.apk > /system/app/launcher2.apk
So there's that. All to restore the Launcher to a version that would allow for a somewhat pointless update. Woo!

[Q] /: files lost on reboot?

My phone has been "broken" for the past 7 days, and I'm having troubles uploading any factoryfs.rfs containing the stock /app and /media folders.
A possible workaround would be flashing as much as needed(sh executable; ls, mv etc) to be able to push the rest through adb.
Pushing the /media folder seemed to be working at first. Here's the issue: when I reboot and execute ls trough adb the /media folder is missing.
I also tried replacing the push command with "mkdir test.d". That folder was also lost on reboot.
When creating the "test.d"-folder in /mnt/sdcard it stayed.
Any suggestions are appreciated.
Another quick question that's too simple to find by googling: does your ClockWorkMod show the option to mount /system at recovery boot? I'm a bit worried since mine does. It could be related to the topic.

SecGallery2_Galaxy.apk deleted from system/app.. Restore possible? [SOLVED]

Alright.. I wanted the Note 8 version of gallery and i went into system/app folder and deleted the SecGallery2_Galaxy.apk but before deleting i saw that its size was 0.00 kb lol ..
But when i tried tried to copy and pasted in the extsd it pasted and showed 13mb..
Now i deleted the file and copied the Note 8 Galley and pasted in the system/app folder only to get an error " Operation failed " and i realized only 7 mb free space is there in the partition by going into the android emulator!
Now i also found out that, full size SecGallery2_Galaxy.apk was in the preload partition and i instead of replacing that i deleted the file in system/app..
Now how do i get back that file in system/app?.. is that what they call deodexed file?.. Please help..
Thanks a lot in advance

Just copy it from other rom, that You can explore with winrar.
Sent from galaxy n7105

The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.

nokiamodeln91 said:
The actual apk was in preload and was symlinked to system partition. Thats why it showed 0 KB in system.
You can get it back by typing in shell
Code:
$ su
# ln -s "Path of apk in preload" /system/app/
And this is not called deodexing.
Click to expand...
Click to collapse
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance

CustomRomAddicts said:
Thanks but i dont know the path.. the name of the file is SecGallery2_Galaxy.apk, so whats the path of the file?..
can u please type and show?..
Thanks in advance
Click to expand...
Click to collapse
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.

nokiamodeln91 said:
I dont remember... but something like
/preload/symlink/system/app/SecGallery2_Galaxy.apk
but double check.
Click to expand...
Click to collapse
It says read only file system
I even changed the permission of the file in preload to 644 ( rw-r--r-- )
still the same message?.. any idea what it might be?.
Thanks in advance

use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.

nokiamodeln91 said:
use adb shell
then mount the preload partition as rw
# mount -o remount rw /preload
# mount -o remount rw /system
the use the codes written above.
Click to expand...
Click to collapse
Honestly i just now searched in google for adb shell and it says to run windows but when i download and double click the adb.exe it runs and exits!.. Please help..
Will mounting the preload and system in recovery and rebooting the device and running the script again in android emulator work?..

Keep in recovery and mount both.. Then run....

nokiamodeln91 said:
Keep in recovery and mount both.. Then run....
Click to expand...
Click to collapse
I tried in adb shell too.. but its not working
Do u guys have the symlink file?.. can u share with me?.. will it work?..
Thanks in advance

Oh Yeah! SOLVED IT!!
I installed Root explorer and created symlink via that and Voila it worked!
Although i dont know why when i open a photo in gallery i experience FC!