After I got my nexus back from HTC for a faulty power button, my nexus has been rooted via a replaced motherboard. Now I have already root my phone and unlocked the bootloader, however when I try to flash the recovery image I get
sending 'recovery' (4074 KB)... OKAY
writing 'recovery'... FAILED (remote: image update error)
Also I can somehow access recovery, and it looks as it should. However when I try to backup my rom it says "Run 'nandroid-moblie.sh' via adb!" and similar things when I try any other the other options. Could someone please help with this?
How are you trying to flash it? Fastboot is the best foolproof way to do flash the recovery. I have never really seen that error before, what recovery are you trying to flash?
Your nandroid error is most likely because the sdcard thinks it's still mounted, or is mounted. Also, I don't know if this still happens but make sure you only do a backup, not backup +ext if you don't have an ext partition on the sdcard.
he's obviously using fastboot...
Did you make sure recovery.img had the right MD5 hashes as amon_ra posted?
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
cajer said:
I have check the MD5 checksums, and they match up. Also, i am using fastboot to flash, and I am trying to flash RA-nexus v2.0.0. Are you suggesting that I remount the sd card to get it to flash the recovery image?
Click to expand...
Click to collapse
I would suggest you try in command line with the adb commands as follows:
adb shell
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
gravufo said:
I would suggest you try in command line with the adb commands as follows:
adb shell
su
mount -o rw,remount /dev/block/mtdblock4 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 775 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
You need flash_image for this, check the wiki for the file...don't forget to put the recovery in the root of the sdcard and rename it to recovery.img for convenience purpose
Click to expand...
Click to collapse
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
cajer said:
What do I do with flash_image? Also this device came back stock with frg 83, which I am trying to flash the recovery on. When I type in adb shell, I get "error: device not found" even though I can see it through "fastboot devices".
Click to expand...
Click to collapse
flash image has to be placed in the root of your sd card as well as the recovery!
As for the adb shell, try enabling USB Debugging in Setting > Applications > Development
Make sure you're rooted too (use SuperOneClick if you're not already)
I can get through that string of commands until
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
Then it says "No such file or directory". I have already rooted, and both the flash_image and recovery file have been placed in the root directory of the sd card.
Well, after you did that string of commands, does the problem persist?
Also, do you have at least 400MB free on your SD card?
Well, I can't get
rm /system/etc/install-recovery.sh
rm /system/recovery-from-boot.p
reboot recovery
to work as it responds with "No such file or directory". Even if I go through after the errors, the recovery still gives 'nandroid-moblie.sh' via adb!" and similar messages. Do I need to find a way to put the file install-recovery.sh in my sd card root directory if so, where can I get it? In addition when I try to flash recovery with nexus one superboot I get "(remote: signature verify fail)" even though the MD5 sum matches up.
Yes I have over 5 gbs on the sd card.
rm = remove
The steps you are trying to perform with the 2 rm command is to remove the 2 files that automatically rewrite your recovery.
If you reboot without succeeding in removing these files, the recovery image you just flashed will be written over by the stock recovery...
Since you have rebooted, and are still having the problem, you need to do the whole list of commands again... be careful how you type...
Sent from my Nexus One using XDA App
Danger, it seems as I can't remove those two files as I get the error message "rm failed for /system/etc/install-recovery.sh, No such file or directory". Any ways to successfully remove them?
Sounds like the files aren't actually there then, unless you're making a typing error...
Did your recovery update after the last attempt? Did it look different, what is the recovery version that is listed on the recovery screen?
Sent from my Nexus One using XDA App
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
cajer said:
I have been flashing different themed recoveries to see if any data transfers, and the background changes. But as before the actions all say "Run 'nandroid-moblie.sh' via adb!" or something similar.
Click to expand...
Click to collapse
if the rm doesn't work it's fine.
But what about your flashing command? It simply works or outputs an error too?
When u flashed themed ones, did the background change?
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
cajer said:
The background did change when I flashed the themed ones, however it still outputs errors like "Run 'nandroid-moblie.sh' via adb!" when i try to run any of the options under recovery. The fastboot flashing command gives this "writing 'recovery'... FAILED (remote: image update error)" error.
Click to expand...
Click to collapse
When you try running a NAND backup or restore a previous NAND?
When restoring, the backup must be at the exact position where it was when you did it: /sdcard/nandroid/HT#####/BCD######
I was trying to backup my current image, and this happens with all other actions even the shut down action on the recovery page just with "Run 'reboot -p' via adb!"
lawl xD that seems useful...
well, that's extremely odd to be honest...uhm...I think you should try and contact amon_ra if possible...He knows the code of his recovery and might know what's wrong...
I really have no clue, sorry =\
PS: Have u tried clockworkmod recovery?
Alright I will try contacting amon_ra, and I will try clockwork tomorrow. I was going for amon_ra recovery to get Sense HD on it with sd partition. Thanks for the help though I learned more stuff about my phone.
EDIT: Wow, clockwork installed like a charm, and I didn't even have to do anything. I'm now a clockwork convert.
make sure to read: http://forum.xda-developers.com/showthread.php?t=971197
the other day I realized that I did not have the OC kernel installed for CM7, so decided it was time to get that on there. I was unable to boot into recovery via ROM Manager or manually (using n+power). ROM manager was telling me 3.0.1.0 was installed, so I was a bit confused about why this was happening. I tried re-installing CWM via adb, that was a no go as well.
I then resorted to irc for help, people explained the proper way to use the key combo and then told me I was lying when I told them I didn't have the "touch the power of reading" splash
video of nook booting: http://www.youtube.com/watch?v=PGScwmoS7HU
so after a bit more poking and questions, found out the splash is within u-boot.bin, and somebody suggested I pull u-boot.bin from stock 1.1 image and push that to /boot.
Code:
1) download and unrar http://www.megaupload.com/?d=D7GFVHCQ
2) adb shell busybox mount / -o rw,remount
3) adb shell busybox mkdir /boot
4) adb shell busybox mv /boot/u-boot.bin /boot/u-book.bin-bak
5) adb push u-boot.bin /boot/u-boot.bin
6) adb shell busybox umount /boot
PROBLEM SOLVED. can boot into CWM after replacing u-boot.bin. I think this was related to attempting to format sdcard within CM7 on nook
So I have the same problem ... "Loading ..." screen and inability to boot into CWM after flashing with ROM Manager.
However your instructions are missing a step. You have the user creating the /boot directory with mkdir but not mounting /boot ... but at the end you have us umount /boot.
I sort of remembered this process from when I installed the HC pre-release, so I found my old bookmark. Following is your instructions with the missing step. Doing this made CWM load for me using power+N
Code:
# download and unrar http://www.megaupload.com/?d=D7GFVHCQ
adb shell busybox mount / -o rw,remount
adb shell busybox mkdir /boot
[i]adb shell mount /dev/block/mmcblk0p1 /boot[/i]
adb shell busybox mv /boot/u-boot.bin /boot/u-boot.bin-bak
adb push u-boot.bin /boot/u-boot.bin
adb shell busybox umount /boot
PS. I'm guessing this still isn't the RIGHT way to fix this issue, as I still can't get the reboot to recovery option working (I'm using CM7 nightly 39). However search function on the forums is offline, I'm very tired, and I'm about to go on a road trip early tomorrow so I'm not going to keep trying to fix it right now. If someone wants to post better info to get CWM 3.0.1.0 and ROM Manager working better for CM7 I'd love to see it. But I got my ALSA update installed so I'm happy for now
I've not been able to use Reboot into Recovery (from holding the power button) for a while now. However, the option from ROM Manager usually works, as does holding the n key while booting.
How can I access the /data/ partition?
I was using the touchpad, installed some apps like teamviewer/unified remote/xbmc from the market, and all was going well and then for no reason the tablet froze, CM9 just stopped responding. So I rebooted it (holding the home button and power button was the only way to get it to do anything) but it's stuck at the Cyanogenmod boot animation. It's been on that animation for 5-10 minutes, so I rebooted again, went into clockworkmod and reflashed the latest nightly and gapps. I then rebooted, android booted up, said it was upgrading/optimizing 77 something apps, then it said it was starting the apps, and then it froze at that point, wouldn't proceed. I then reboot and am stuck at the boot animation again. My best guess is that one of the apps I installed is hosing it. I plugged the usb cable in and normally during the boot animation of my phone I can adb logcat but I can't seem to adb detect this device during boot animation. Windows see's it as a MTP device but no filesystem comes up in my computer. So adb logcat and adb shell so I can get into /data/app to wipe out the last few apps I installed won't work, but on my phone I can also adb shell in from CWM. So I rebooted into CWM but when I connect the cable to the laptop it still doesn't see it as an Android ADB device. No adb shell. Not like my phone at all.
So back to my original question, short of wiping /data from CWM, is there anyway for me to get at /data/app to delete some files? I'm curious what's causing this.
You can do an and pull from clockwork mod or have you tried mounting it on the computer from the clockwork mod options?
I've mounted before in clockwork but only sdcard, so that i can put a zip on it to flash. Can you also usb mount the /data partition?
Sent from my SGH-I777 using XDA
If you can reboot into WebOS, I know a way you can mount it and grab what you need.
Boot into WebOS, and connect your tablet to your PC. Then start up Novaterm (C:\Program Files\Palm, Inc\terminal\novaterm.bat). Connect to your tablet.
From there, you'll be at a root prompt. This is good. Type the following commands:
- mount /dev/mapper/store-media /media/card
- mount /dev/mapper/store-cm--data /media/hdd
- cd /media/hdd
- mkdir /media/card/cmdata (this will make a backup folder for you)
From there, you can use basic linux commands to copy files from your data partition to your media card. The ones you should need (forgive me listing the extra commands, even if you know them):
- ls (LS) will give you a directory listing
- cp -r <Folder> /media/card/cmdata (this will backup whatever folder you wanna backup to the cmdata on your card)
- rm -r <folder> (this will remove whatever folder you wanna remove)
- rm <filename> (this will remove whatever file you wanna remove)
I just tested this method, and it allows you to back up whatever you want, as long as you can get into your /data partition. You can do whatever you need to do. Just be careful you don't remove something you don't have to.
Hope this helps you, mate. If so, hit Thanks, if not, drop me a PM and we'll discuss other options.
glitchsys said:
I've mounted before in clockwork but only sdcard, so that i can put a zip on it to flash. Can you also usb mount the /data partition?
Click to expand...
Click to collapse
Yes, you can, but you can only read it from a Linux PC. A Windows system will not be able to access the partition, because it is an ext3 filesystem.
You can also use the "USB mode" used to install CM, but it will run into the same problem. Without Linux, you will not be able to access files.
I would clear the cache, that usually seems to solve these kind of issues. (Of course it could also mess it up further...)
My HTC ONE wont mount via usb so i'm trying to flash a custom rom to the phone's internal storage (as it has no sdcard slot)
I have got as far as opening the CMD and directing it to the device but i dont know the proper command to ADD a zip file to the storage
anyone pls help, i think this is fairly simple
You're supposed to be using ADB commands in order to sideload a ROM and then install it from recovery.
Is that what you are trying to do or how are you going about it? Are you trying to use fast boot commands? Because those won't work.
Here's a guide to setting up ADB:
http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
You'll need proper drivers for your computer to recognise your device in ADB mode, and those are automatically installed with HTC Sync Manager.
After placing the ROM file into the platform-tools folder, rename it to rom.zip and then execute the following command:
adb sideload rom.zip
Of course that's after making sure that your device is actually recognised by ADB and listed in command prompt, by using this code:
adb devices
Good luck
Ok great i think i have adb and most of the drivers already installed so i'll give this a go.
yes my ONE got stuck in bootloop with CM10.1 and my backups are on my PC not the phone so i figured i'd mount by USB but neither TWRP or CWM will mount by USB????
I have CWM touch installed so i'm thinking as long as this is in place my device isn't tottally shafted?
Use the command:
Code:
adb push name_of_rom.zip /sdcard/0
or
Code:
adb push name_of_rom.zip /data/media
when you're in CWM, then flash the rom
Drag and drop it to the storage folder. Should be
/storage/sdcard0
And you can use ftp WiFi from the playstore if you don't wanna connect via usb cable.
I've resolved this now.
i'll explain what i did, it may help someone else out:
I went into CWM
Then i formatted the internal sdcard
Once i did that, an option in CWM appeared to sideload zip, i picked that, then it waited for the sideload command
went to folder on my PC containing adb.exe > hold shift > right click > open command here
then typed "adb sideload <romname>"
thanks for the help, good community here.
Yes, that's the correct way. And by the way, you cannot mount usb storage while you're in recovery anymore, neither TWRP nor CWM will do that for you. The only other option is using an OTG cable.
My friend has an HTC Vivid that is stuck in a boot loop - it only boots into the recovery mode (CWM-Based Recovery v5.5.0.4). A bi difficult to troubleshoot over Skype, but I tried a few things.
The recovery can't mount /cache. Tried to run backup and got "Can't mount /system!"
adb sees the device, but I can't cd into /data/data to copy mmssms.db or the contacts.
I tried running 'su' in adb shell, but it wasn't found. Indeed, the 'bin' directory was empty.
Any way of pulling /data/data/com.android.providers.contacts/databases/contacts2.db ? Or otherwise getting the phone to boot?