Got bored of searching and googleing... but using MoDaCo's WIP R4 FroYo ROM and Clockwork Recovery... when I flashed the ROM I lost the boot time animation (the PC BIOS one) so tried to put it back in recovery using adb push *file* /data/local (file copied ok) but still only have the htc boot screen also tried pushing the file with the phone booted, but again no dice
Anyone got any ideas?
Thanks in advance
------ Resolution ------
Ok, firstly massive thanks to those who helped - you are what xda is all about ... I finally managed to resolve this problem by
adb mount /system
adb shell
looking around and removing all bootanimation.zip's I could...
then exit the shell session and adb push the bootanimation.zip to /system/media
adb reboot and
I found this info here: http://androidforums.com/all-things-root-droid/97562-froyo-boot-animation.html
Not sure why this keeps changing? Maybe it is something specific to the Modaco R5 ROM?
Try pushing it to /system/customize/resource
yes the directory for froyo is the
/system/customize/resource
thanks for the assist guys, I tried this in recovery
"adb push bootanimation.zip /system/customize/resource" which went ok, the adb reboot and no show with the new boot screen any ideas??
Many thanks
first of all
mount the /system
then the path should be /system/customize/resource/bootanimation.zip
still cant get it to work I'm afriad
Here is what I did...
reboot to recovery (clockwork mod)
adb shell mount /system/
adb push bootanimation.zip /system/customize/resource
adb reboot
and no new boot animation
any ideas what I'm doing wrong?
Ok, found this http://forum.xda-developers.com/showthread.php?p=7239986 - booted to clockworkmod recovery and tried:
adb shell
mount /system
and got "mount: mounting /dev/block/mtdblock3 on /system failed: Device or resource busy
MadMic said:
still cant get it to work I'm afriad
He is what I did...
reboot to recovery (clockwork mod)
adb shell mount /system/
adb push bootanimation.zip /system/customize/resource
adb reboot
and no new boot animation
any ideas what I'm doing wrong?
Click to expand...
Click to collapse
Is that a typo? the path for the first adb command entry should be 'adb shell mount /system', not 'adb shell mount /system/'
Also, where are you placing the bootanimation.zip file? try placing it directly to the C: (C:\bootanimation.zip) and try executing the commands again.
MasDroid said:
Is that a typo? the path for the first adb command entry should be 'adb shell mount /system', not 'adb shell mount /system/'
Also, where are you placing the bootanimation.zip file? try placing it directly to the C: (C:\bootanimation.zip) and try executing the commands again.
Click to expand...
Click to collapse
Thanks for the reply -
The bootanimation.zip is in the same folder as adb... it says xxx bytes copied which is the same as the file size... I've tried with /system with and without the trailling / still no joy..
If I do adb shell mount /system in recovery I dont see anything... but if I do adb shell [enter] then the commands I see the error about the device being busy...
Is there anyway to do this from a terminal app in the phone directly?? I seem to recall there is but cant find it...
Thanks for the help guys
http://psfreedom.com/wiki/index.php?title=OpenDesire4.0.4
http://www.ps3hax.net/showthread.php?p=123003
Im trying to install this recovery so i can jailbreak my PS3, but when i try to use unrEVOked, it hangs while pushing the recovery
When i try to use adb on both my phone and my computer it says i have no space!
what should i do?
EDIT:
fastboot erase recovery
fastboot flash recovery recovery.img
sounds like it would work, bu t i dont want to risk that lol
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
SwordOfWar said:
The no space error will happen if you don't mount system as writable. By default it is set as read only.
Read around to lookup the command to remount system as writable. The command varies depending on your device.
For the motorola droid I used the following:
mount -o remount,rw -t yaffs2 /dev/blockmtdblock4 /system
I think the G1 and other HTC phones use mtdblock3 instead of mtdblock4, but I'm not sure.
Click to expand...
Click to collapse
Alright, thats good to know. Ill look around
http://forum.xda-developers.com/showthread.php?t=770663
"You can only write to system on the desire via adb from recovery."
So i do what? boot into recovery, plug in my phone and adb it again?
flash_image recovery image.img?
Hmm, guess not.
I booted into recovery. Plugged my phone in and did an adb devices. It said one device called recovery
i did mount /sdcard (apparently i dont have to mount it to a location)
i cd'd into thte sdcard and did a flash_image recovery psfMod.img and it said i had no space
I was also looking at this
http://forum.xda-developers.com/showthread.php?t=770663
but i still cant get it to work.
do i have to have s-off?
So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Thank you very much for putting this together
I am one of the curious one too.
You saved me....
If you can't get into recovery, I'm sure you can flash one through fastboot. No?
Sent from my VM670 using XDA App
Hi!
I had stock rom, but my phone was rooted.
So if whenever I turn my phone on, it goes to Clockwork Mod, does that mean it is bricked?
And will there be any way to unroot my phone after I do this? BC my 3G wasn't working at all, it should be working, but its not, so I did a factory reset.
Didn't work for me
when typing su after nand restore i get
/sbin/sh: su: not found
Ok so I have followed the instructions to the letter. And am attemptingto access adb shell. But in cmd prompt when I type adb devices it comes up with list of devices attached and says nothing. So how are we supposed to be accessing adb shell?
In clockworkmod, I went to the option for mounting and mounted the sd card, and a folder popped up on my comp, and there was no folder called Nandroid or clockworkmod
Any help guys?
I don't understand how to do the Nandroid instructions part... do I have to go to ADB?
atr0phy said:
So everyone says never do this, but what can I say, I was curious
My Optimus was previously rooted using sublimewolf's method: http://forum.xda-developers.com/showthread.php?t=935312
I then proceeded to brick it by using the Factory Reset found in the Privacy Screen. This forced my phone into a recovery loop.
If you can't even get to your custom recovery, your phone might be your newest paperweight But as long as you can both get to recovery and access the phone via adb, you'll be okay.
So here's how to unbrick it:
This is the flash_image: http://www.mediafire.com/?bx14hzq5i2pq3ps
And here's the stock recovery image + nand backup: http://www.mediafire.com/?ac0e2ksq0eslytk
(In my case, I was able to skip to Step 4 in the Nandroid Instructions because I had performed a Nand Backup when I rooted, therefore the necessary files were already in place)
Nandroid Instructions:
1) Unzip both downloaded archives
2) Move the BCDS-20110203-0357 dir into /sdcard/nandroid/mem=477M (also extract recovery.img and flash_image to root dir of your SD card, as you will need to later anyway)
2a) For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup
3) Mount SD into phone if it isn't already, boot into recovery if your phone isn't already there
4) Go into the "Backup/Restore" menu, and select "nand restore", confirm and wait
5) Reboot, proceed to Recovery Instructions below
Recovery Instructions:
1) Extract recovery.img and flash_image to root dir of your SD card if you haven't already done so
2) Connect to your phone via the adb shell and input the following commands:
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5
# flash_image recovery /sdcard/recovery.img
# reboot recovery
3) If everything was done correctly, your phone should boot up normally to the OS
If the links above go down, let me know and I'll re-up
(thanks to tankhull for putting this info together)
(oh and you're welcome for being a guinea pig )
Click to expand...
Click to collapse
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Wreak_Peace said:
In the nandroid instructions, for placing BCDS-20110203-0357 into the /sdcard/nandroid/mem=477M
Do I have to do that, or step 2a if I have Clockworkrecoverymod, "For Clockwork Recovery, place the BCDS-20110203-0357 dir into /sdcard/clockworkmod/backup"
Also, how do I put this directory into the /sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M
Do I use ADB? And if so, how do I, because I have no idea about what commands/etc to use.. or could somebody please link me to a guide on how to push a file/folder into a folder like the ones I previously mentioned (/sdcard/clockworkmod/backup folder or /sdcard/nandroid/mem=477M)
Thank you in advance for your help!
Click to expand...
Click to collapse
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
mmarz said:
You are making this harder than it has to be. All you are trying to do is place a folder and some files on your micro sdcard. Place the micro sd card on your computer. Grab the folder "BCDS-20110203-0357" and drag it to "/sdcard/clockworkmod/backup" (yes, that one because you have the clockworkmod recovery). If you have no way of placing the micro sd card onto your computer (card reader, micro sd to sdcard converter), then leave the card in the phone, connect the phone to your compter via USB, boot into the recovery, and then turn on USB massstorage mode through the recovery options. This should make the micro sd card pop up on your computer like a usb harddrive. Drag and drop the files.
Click to expand...
Click to collapse
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Wreak_Peace said:
I put my microsd card into my computer, and there are no folders called sdcard, clockworkmod, or nandroid :/
Click to expand...
Click to collapse
Lol, first off, the sd card IS the folder "sdcard". That will only show up on your phone. Secondly, if the folders aren't there, just make them. They are not magic folders. Just right click, and select new -> folder, and name them as described.
clockworkmod\backup\
And then copy "BCDS-20110203-0357" into the "backup" folder.
You do have the Clockworkmod Recovery, right?
I do, and now, when i opened up my cmd
I did "cd c:\android\platform-tools"
then "adb shell"
then this came up "~#"
so even then, I went ahead and did "su"
and it said,
"su
/sbin/sh: su: not found"
So, what do I do now?
and I went ahead anyways did the next step
i typed in "mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system"
then it said
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
(next line) mount: mounting /dev/block/mtdblock5 on /system failed: invalid arguement"
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Wreak_Peace said:
So I just do
"cd C:\android\platform-tools
adb shell
flash_image recovery /sdcard/recovery.img
reboot recovery"
Or do i add the su in an additional line after adb shell
?
Click to expand...
Click to collapse
You don't need the su because you already have the "#" sign. That means you have super user privileges.
mmarz said:
Try doing only the last two lines,
Code:
flash_image recovery /sdcard/recovery.img
reboot recovery
Click to expand...
Click to collapse
K, so this is what I came out with when doing what you said.. this is without typing in su after adb shell.
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
This is what I came up with when i did type su after adb shell..
Code:
cd c:\android\platform-tools
c:\Android\platform-tools>adb shell
~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
failed with error: -1
error opening /sdcard/recovery.img~ # reboot recovery
reboot recovery
c:\Android\platform-tools>adb shell
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
mmarz said:
I've never done this method so I can't tell you why it is not working or how it should work. Sorry.
I do have my own method for solving the bootloop issue. Try flashing this with your recovery: http://www.mediafire.com/?fbaoutnaw717pnb
Place it on your SD card and then use your recovery's flash zip option to flash it. It has helped others. It will replace your recovery with the Xionia recovery. If it works, you should boot into the LG logo. Once you can do that, boot into your recovery by using the correct button combo and flash any rom that you want to use.
Click to expand...
Click to collapse
So i extract it to root of the micro sd? all of it? and then instead of recovery.img its vrecovery.img?
And so if it replaces my recovery with xionias recovery, it will boot into android and I can use my phone normally?
After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......
i flash manually the files from recovery so now im ok.
Steps
1)Download this file (has everything you need) http://d-h.st/RLS
2)Unzip it
3)Boot Into recovery
4)Open a command promt on the unziped folder
5)Copy paste one by one these commands into command promt
Code:
adb shell mkdir /storage/sdcard1
adb shell mount /dev/block/mmcblk1p1 /storage/sdcard1 -t vfat
adb push part1.sh /tmp/part1.sh
adb shell chmod 0777 /tmp/part1.sh
adb shell /tmp/part1.sh
adb push persist /storage/sdcard1/persist
adb push customfs /storage/sdcard1/customfs
adb push fsg /storage/sdcard1/fsg
adb push fsc /storage/sdcard1/fsc
adb push ssd /storage/sdcard1/ssd
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/persist if=/storage/sdcard1/persist
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/customfs if=/storage/sdcard1/customfs
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsg if=/storage/sdcard1/fsg
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/fsc if=/storage/sdcard1/fsc
adb shell busybox dd of=/dev/block/platform/msm_sdcc.1/by-name/ssd if=/storage/sdcard1/ssd
You are ready
i have same problem with z7 max but in mine situation i cant see sim cards
can i use the same?
Petros_tigra said:
After repartition of internal memory i cant enable wifi and bluetooth.From that i understand the script didnt make proper backup and restore of
:customfs.img
fsc.img
fsg.img
parinfo.img
persist.img
ssd.img
Does anyone know how to flash again these file or whole system?
I had already used:
1)nandroid restore from previous condition
2)flash stock rom from stock recovery with no success...
Every opinion will be helpful......
Click to expand...
Click to collapse
hi ,
i have zte nubia z7 mini and i was installing z5s mini miui rom in my phone. when the process done phone went to off and hard to turn it on. when i connect to pc it doesn't even detect the phone usb and asking for installing phones usb drivers... please help me if its possible
Thank you Sir!
Your intelligence has saved my Z7 Max running stock ROM v1.59. Now the WiFi and Bluetooth is working as usual....
Can you please help me about this, i tried to repartiton the phone and i got the same situation phone works but wifi and bluetooth doesnt work, i try to download that link but it says link doesnt work any more files are missing. can you please help me about this.