Error result
I can not come at stock recovery boot. Neither with Volume down & Power Keys nor with titanium menu.
Software Release
_130_WE
What is happend until the present time:
start within _0126 one successfully
after this repeatedly with wrong key combination power & volume up unseccessfully
update to _0130_WE
execution of code (see below) with _0130_WE original data install-recovery.sh and recovery-from-boot.p
Code:
adb push recovery-from-boot.p /data/local
adb push install-recovery.sh /data/local
adb shell
su
# mount -o rw,remount /system
# cat /data/local/install-recovery.sh > /system/etc/install-recovery.sh
# mv /data/local/recovery-from-boot.p /system/
# dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1
755+1 records in
755+1 records out
386815 bytes (377.7KB) copied, 0.593557 seconds, 636.4KB/s
I am in a state of confusion.
If I try a recovery boot the screen winces a short time before nvidia green logo appears and the TPT goes to normal mode.
Problem solved.
After dd start install-recovery.sh one again.
Wrong key combination.
mobil geantwortet
Related
i try this on the comment prompt while phone running.
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
and it'll say:
rm failed for -f, read only file system
it wont let me write on the system im guessing.
Now i tried doing the same thing but phone mode is on recovery.
I have the nand protection unlocked so when i get to recovery mode
i have already the custom recovery setup showing, i don't run the recovery-windows.bat.
now when i type this on the comment prompt
cd\sdk
cd android-sdk-windows
cd tools
adb devices
adb shell
#mount /dev/block/mtdblock4 /system
cd /system/app
ls
i get all the apk. files
i try removing an apk.file
typing this syntax:
rm -f thenameoftheapp.apk
after i hit enter it shows me
#
so im assuming the apk. has been removed
after i exit the comment prompt and i wipe the dalvik-cache
i reboot the phone and all the apps i removed are still there and running still.
help please
Okay guys.. I successfully rooted my phone and I removed a bunch of apps and stuff. one of the apps that i removed was Mediascape. I couldn't find a better media player so i attempted to restore the app using this in cmd:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
After my phone rebooted.
As it was starting back up, the sony ericsson logo appeared (and i could hear the phone connect to my computer) but then it would end up going to a black screen. And it has been stuck on that for 5 minutes. I can still enter commands, but other than that, I have no idea what is happening. Anyone willing to help me out?
I've also tried removing the app again, but no go
EDIT
NEVERMIND. I got it to work again....
sorry about this, I kind of had a panic attack haha
1. Prepare a short mp3 and name it android_audio.mp3
2. Put the mp3 under the adb folder
3. Save the following code as !bootaudio.bat (I use this name)
4. Turn your phone into ADB debugging mode
5. run !bootaudio.bat
6. Reboot your phone and have fun!
This should work on almost all G7
Tips: During the boot animation, the volume would change twice. So I suggest insert 1 second before the audio for escaping from the volume changing side-effect.
Code:
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
adb shell rm /data/local/android_audio.mp3
adb push android_audio.mp3 /data/local/
adb shell rm /system/customize/resource/android_audio.mp3
adb shell ln -s /data/local/android_audio.mp3 /system/customize/resource/android_audio.mp3
adb shell ls -l --color=never /data/local
adb shell ls -l --color=never /system/customize/resource/
adb pull /system/customize/CID/default.xml
pause
Script description:
Mount the system path to enable writing access.
Remove the original boot sound if it exists.
Push your mp3 into the data/local, where the bootanimation.zip is.
Make a link to data/local/android_audio.mp3
List the two affected pathes for you to confirm the result
Pull the default.xml out from the phone, if you find it not work after reboot, you can check the xml to see what the actural fullpath it is using. And manually change the script to try again.
My current boot sound is attached to the thread.
Hi there, I have an error when trying to link beacause the folder does not exist... may I create it manually?!
Hi there!
I upgraded my wife's tattoo's recovery to 3.0.0.6 using ROM Manager, unaware that I will not be able to flash ROMs anymore (amend / edify scripting differences)
Now I cannot find a way to revert to original/older recovery, did try a lot of stuff around here and still no luck
Cannot flash using RUU as i receive a "Wrong bootloader error"
Any help would be appreciated.
Thanx in advance.
Adrian
________________________________________________
LE: After trying for some weeks now, I decided to post this message - few minutes after, I solved the problem - like this:
Code:
C:\>adb push c:\flash_image /sdcard/
365 KB/s (26172 bytes in 0.070s)
C:\>adb push c:\rtattoo\recovery.img /sdcard/
905 KB/s (3731456 bytes in 4.025s)
C:\>adb shell
# su
su
# mount -o remount, rw /system
mount -o remount, rw /system
# cp /sdcard/flash_image /system/bin
cp /sdcard/flash_image /system/bin
# cd /system/bin
cd /system/bin
# chmod 777 flash_image
chmod 777 flash_image
# flash_image recovery /sdcard/recovery.img
flash_image recovery /sdcard/recovery.img
Thanx - OP please close.
why so much on typing CMD adb
use android commmander It is Great
You can try to use this script http://forum.xda-developers.com/showthread.php?t=644279 but replace the recovery file with the original recovery file . don't forget to rename it to the same name.
My phone has not been able to receive calls because the default APN settings from LOS are just wrong. I updated the file (/system/product/etc/apns-conf.xml) in recovery, but after a reboot, the file is back to what it was before I changed it.
I am using LOS recovery if that helps. How do I change that one file to have it persist across reboots?
Thanks
Problem solved!
Had to mount the "/" partition to be writable using the command:
Bash:
adb shell su -c 'mount -o remount,rw /'
Then after making changes, I first pushed the file to internal storage:
Bash:
adb push ./apns-conf.xml /sdcard/Documents/apns-conf.xml
Then finally I copied it to the proper location:
Bash:
adb shell su -c 'cp sdcard/Documents/file.xml /system/product/etc/apns-conf.xml'
Hope that helps someone