My SGS shows the boot up screen/noise, then just sits on a black screen and vibrates occasionally
I'm able to press the 3-buttons and boot up into ClockworkMod Recovery, however nothing seems to fix it. I've tried applying update.zip, wiping cache, factory reset, loading the restore-update.zip, and "restore" to the only checkpoint, but nothing works.
I screwed up when installing a theme, these were the first part of the directions:
1. adb shell
2. su (grant su rights on your phone when asked)
3. mount -o rw,remount /dev/block/mtdblock3 /system
3. rm system/framework/twframework-res.apk
4. rm system/framework/framework-res.apk
5. rm system/app/settings.apk (if no file is found try Settings.apk ... no ide if it matters tho)
Click to expand...
Click to collapse
I got this far, then realized that the files I needed to replace those with were on the internal SD, but IN A ZIP. So I couldn't use them. RMing the old ones meant nothing worked anymore.
Now my phone is in debug mode, can't seem to get su access (although I can use adb to a limited extent), and I can't get it to work
Any help for me?
I have3 the same problem Have you found out how to fix it?
Looks like your going to have to use odin to reflash ive had this many atime from unsuccesful modding and always worked.
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.
so i dropped my phone and the screen is completely dead. the phone itself works fine because i see trackball notifications and logging using adb logcat. i can also browse the filesystem through adb shell. i plan on sending it back to HTC for repair, but before i do that i wanted to create a nandroid backup. im running CM7 RC2 and clockworkmod 3.x. i boot the phone into recovery, and confirm it's in recovery because adb devices shows me:
Code:
List of devices attached
HTXXXXX recovery
then i try running: "adb shell nandroid backup", but that gives me:
Code:
E:unknown volume for path [/sdcard]
Can't mount /sdcard
even though /sdcard is mounted. i tried unmounting /sdcard and then running it again but i got the same error.
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...)
Hi developers. I am sorry for posting this. I spent the last week trying to solve it by myself with no hope. This is my second time installing something on a phone, but it is my only phone, so I beg anyone for a help...
-What I did:
Some days ago I downgraded to this ROM C5503_10.1.1.A.1.310_GLOBAL-LTE.ftf to use DoomLord rooting script. I did it with flashtool for linux and I applied his .bat step by step in the terminal since windows would not detect my phone.
It worked. I had root for some days, but I was still annoyed by sony default android. So I decided to install Cyanogenmod.
I unlocked the device with sony official system and wen't straight to this instructions, before the first reboot
wiki.cyanogenmod.org/w/Install_CM_for_yuga
I booted succesfully in CWM, followed everything as it says there. But that's where weird things happened:
-The problems:
-The backup
I tried, it wouldn't mount /sdcard. Since I don't understand much about this, I thought it was normal. The next choice was sdcard1, I backed up there. Or so I thought...
-The factory reset
I factory reset, again, not mounting sdcard. Here is the message that shows when I try this now:
can't mount /data!
Error mounting /sdcard.android_secure
Skipping format...
Data wipe complete.
Since it said it is complete, I went on installing the zip file from my sdcard1. Both CM 10.2.1 (dogo, the right one for my phone) and the appropriate GAPPS.
Now it loops on the CM loop animation and I have to remove the battery...
-The restore problem
It still boots on the recovery mode. So I tried recovering my backup from sdcard1. But the image name is 1970.01.01.00.03.16. And it says "md5 mismatch"
I tried flashing again the stock rom with flashtool. The proccess goes on but nothing happens. I still have CWM and the boot loop.
I read elsewhere someone with a similar problem who solved using sony "emma" software. I installed it, it won't even recocnize my phone.
It recocnizes that there is a phone, but don't know which one.
But that has alway been the case with windows. I haven't been able to do anything in windows other then accessing the sdcard (when the phone worked).
Is there something I can do? I imagine that somehow, for some reason, the /data and /sdcard partitions got corrupted. I imagine I would need to repartition this and install again, but I have no idea how this happens on phones...
I can mount /system /cache and /storage/sdcard1. just /data I can´t. Says "error mounting /data"
This is my only phone and a vey recent $400 thing. I was very stupid to do that withouth a replacement and really need this phone. I greatly appreciate any help...
I found this post forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ searching the internet. Is it possible that this would solve my problem? or would it finish bricking the phone?
Here's what you'll need:
Working recovery, basic knowledge of adb & the shell
Parted (download here)
stock PB31IMG.zip
Note also that I had run unrevoked forever (so my phone was S-OFF) ... I'm not sure if that's required or not.
So, grab parted from the link above. Now you need to extract the individual binaries from the .zip (the 6 files in the sdparted folder within the zip), ideally to your android-sdk\tools directory. Now push all 6 files (adb push [file] /sbin/). Next, we need to make them useable, so go into the shell (adb shell). Change to your /sbin/ directory, and run: chmod 0755 <file> on each of the 6 files.
Now, we need to fix the partitions. This is assuming that the partitions are there, just the wrong format (which is what happened to me .. I accidentally made them FAT32 instead of ext). So, run the following: parted /dev/block/mmcblk0 mkfs ext2. It will ask if you want to continue, hit yes. When it asks for the partition number, enter 1. Next, when it asks for the format, enter ext2. Let it do its thing. Now, once it's done, run parted again. This time, enter partition 2 (everything else is the same).
Click to expand...
Click to collapse