SO i followed the instructions:
a) rooted with gingerbreak
b) Followed instructions
$ su
# mount -o remount,rw -t yaffs2 (your device /system path) /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# flash_image recovery /sdcard/(your device recovery.img name)
# sync
c) Went into recovery mode (took backup)
d) Applied cyanogen_thunderg-ota-eng.mik-6.5.7, gapps-gb-20110429-signed
e) REboot
CM7 logo comes at boot but hangs there, doesnt go any further..Please help
Wipe cache, dalvik-cache, data in recovery.
Also, adb logcat is a helluva lot useful to watch what the phone is stuck at (or not).
Here are the options I see
Wipe All Data/Factory reset
Wipe /data
Wipe /cache
Wipe /sdcard/.android_secure
Wipe /sd-ext
Wipe Dalvik-cache <<< DID this
Wipe battery stats
Wipe Rotate settings
Where is data in recovery? is it the /data option?
EDIT: working now..OMG had a heart attack for a min
Also didn't use adb, use the simulator instead
Related
Hello,
I restore my original rom and I have only to remove the custom recovery menu to return my phone in original state. I want to return in original state because I need for waranty service. So can someone help to remove custom recovery menu? I think that my USB port on phone is brick and I have problem with display.
Did you backup your original recovey before installing the custom recovery?
No. If someone has it could you share with me the file and short explanation what to do.
I will send you my original recovery. And I will tell you how to flash it. Lemme reach my home.
Sent from my LG-P500 using XDA App
EDIT: you "might brick your device". not my responsibility.
My original Recovery - http://rapidshare.com/files/450046207/original-recovery.img
Now to flash it -
1) - Copy it to the "Root" of your sdcard
2) - Open adb or terminal emulator and type the following
Code:
flash_image recovery /sdcard/original-recovery.img
[source http://forum.xda-developers.com/showthread.php?t=900905 ]
Again "Do it at your own risk"
I will try and i post what is the result.
This is a better way to revert everything to stock. As long as you read all the comments properly, it also removes any custom roms you may have.
So in terminal emulator I will write:
<su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/original-recovery.img
reboot recovery>
or it is enough only
<su
flash_image recovery /sdcard/original-recovery.img
reboot recovery>
I do it with terminal emulator with this comand:
"su
flash_image recovery /sdcard/original-recovery.img
reboot recovery"
and all is like stock state. Now I will go to bring the phone to the shop.
Glad I could help. Good luck
OBJECTIVE - Install CyanogenMod 7
http://forum.xda-developers.com/showthread.php?t=946354
Obstacle - Failed at INSTALLING A CUSTOM RECOVERY
http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
1. I have successfully root by following this guide
http://forum.xda-developers.com/showthread.php?t=1001713
2. I have placed both flash_image and recovery-RA-GNM-thunderg-1.1.0at the root of sd card
http://forum.xda-developers.com/showthread.php?t=1007244
3. I am stucked at "INSTALLING A CUSTOM RECOVERY" and need help (I am getting error messages of file not found. Pictures attached)
Picture 1:
http://www.flickr.com/photos/[email protected]/5562426547/
Picture 2:
http://www.flickr.com/photos/[email protected]/5563002890/
Picture 3:
http://www.flickr.com/photos/[email protected]/5563002928/
PS: My phone is still locked to Koodo, does it matter I leave it locked ?
I think '>' has error
You'd better typing it in terminal no in cmd
need root and type in terminal
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
It will help you
sondw said:
I think '>' has error
You'd better typing it in terminal no in cmd
need root and type in terminal
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
cat /sdcard/flash_image > /system/bin/flash_image
chmod 755 /system/bin/flash_image
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
flash_image recovery /sdcard/recovery-RA-GNM-thunderg-1.1.0.img
reboot recovery
It will help you
Click to expand...
Click to collapse
Thanks and it works.
This thread is an all in one recovery thread.
Prereqs:
1. You must have a rooted device
2. Adb setup on computer (terminal on phone can be used in place of adb but adb is preferred)
3. Phone charged 30% or greater is required to use nandroid.
Supported devices:
LG Ally (aloha)
LG Optimus S
LG Optimus V
LG Optimus M
LG Vortex
LG Chic (alessi)
LG Optimus P500, Optimus T P509 (thunderg)
HTC Droid Incredible See link here Xda
LG Shine Plus
Gz'One Commando (in testing)
Want to submit a new device see thread here : How to submit a new device for recovery creation
Recovery Features:
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
(dinc only) mount /Emmc
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup to restore
As of 2.2.1 sd-ext is backed up as whole so link2sd users should work fine
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse. (Fixed dir-browsing)
Flash Zip From Emmc (Dinc only)
Toggle Signature Verify : Turn of signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe .android secure : Wipes froyo native .android_secure on sdcard
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (requires kernel support for ext4 which all but shine have)
Mounts:
Gui mounts to avoid typing in terminal to mount and cd into a dir to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix apk uid mismatches
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Wipe Sdcard
(Dinc only)
Format /data as ext3 | ext4 : format(reformat) /data between ext3,ext4. (This wipes /data also) Requires modification of init.inc.rc & and compatible rom kernel see dinc thread link above
I have included flash_eraseall binary to recovery which can be used to fix/erase corrupted partitions that will not mount correctly to nandroid restore to.
Useage from adb shell is : flash_eraseall /dev/mtd/mtd4 (where mtd4 is the number of the partition from "adb shell cat /proc/mtd" you want to erase)
Trouble Shooting:
1. Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log. It should have detailed cause of error.
2. If you get an out of memory error reboot device and do it on a fresh reboot.
3. If you get a file not found on the "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak" skip it and move to the next step as this file will not be in your rom unless it has recieved an ota-update and if so needs to be disabled.
4. Permission denied means you are not root user (#)
5. If rebooting into recovery you get a little android guy with a ! and does not look like picture above you still have stock recovery and did not remove the install-recovery.sh.
6. You did check the md5sum for a match before flashing correct?
Please check all the above issues before posting. This is the format I request to be used for troubleshooting.
Device :
Recovery Version :
Error :
Please upload the recovery.log AS AN ATTACHMENT that you moved to sdcard and read. Posts without this log will be ignored!!!
Please no PM's!!!!!
Device system paths:
Ally: /dev/block/mtdblock4
Optimus M: /dev/block/mtdblock5
Vortex: /dev/block/mtdblock4
Optimus V: /dev/block/mtdblock5
Optimus S: /dev/block/mtdblock5
Optimus P500/Optimus T: /dev/block/mtdblock1
Chic: /dev/block/mtdblock1
Shine Plus: /dev/block/mtdblock1
Directions to flash recovery:
Download your device specific recovery and check md5sum for a match before flashing. Download flash_image.zip and unzip it to root of your sdcard. (Not in any folder)
Copy your devices recovery.img to root of sdcard.
Below can be done via adb shell or terminal emulator on phone via root # shell not a $ shell
Note do not type the # or $ as they are for reference only!
Code:
$ su
# mount -o remount,rw -t yaffs2 (your device /system path) /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# flash_image recovery /sdcard/(your device recovery.img name)
# sync
Example for LG Ally above would be:
mount -o remount,rw -t yaffs2 dev/block/mtdblock4 /system
Device specific recovery keys:
Key mapping for Optimus Line & Vortex:
Move up & down = Vol-up & Vol-down
Select = Menu
Backup = Back
Boot recovery from device off: Vol-down + Home + Power and release at LG logo.
Chic(alessi): Vol-up + Vol-down + Power
LG Ally & LG Shine Plus:
Move up & down = Up & down on sliding keyboard
Select = Enter on keyboard
Backup = Vol-down
Boot recovery Ally: Send + Menu + Power
Boot recovery Shine Plus: Vol-down + Home + Power
Adb reboot recovery can also be used to boot custom recovery on most devices.
WARNINGS:
Do not flash a radio.img
Do not factory reset your device via Android OS. Use wipe in recovery.
Source for recovery & recovery kernels My Github
I want see exact percent in my battery icon, i tried some zip from user jokersax11 but i guess are for deodexed phones.
Thanks.
Check details in post 4.
Get the "Battery" app in the Play Store, the developer's name is Macropinch... shows the exact battery %..no root needed
Sent from my MB855 using xda premium
Details
1.- download e install rsd lite and ADB drivers
2.- go to: http://forum.xda-developers.com/showthread.php?t=1202666&page=109 an download 1FF-sunfire-user-2.3.4-4.5.1A-1_SUN-198_7-CM-release-keys-signed-Sprint-US.sbf.gz (extract it) and Stock Deodexed and Zipaligned 198_7 ROM Working Data
Power off your photon then put in rsd mode hold vol + & power button, connect it to usb port and flash with rsd lite.
3.- root with this package: http://www.mediafire.com/?195zmexjqjqvq0g for more details steps check this topic : http://forum.xda-developers.com/showthread.php?t=1819660
4.- Extract app & framework folders from Stock Deodexed and Zipaligned 198_7 ROM Working Data and copy to sdcard, enable in your photon USB Debugging by going to Settings > Applications > Development and checkmark USB Debugging option, connect your phone to the computer but do not mount SD Card or SD Ext.
5.- change to ADB dir and then execute:
adb shell
su
stop
mount -o rw,remount -t emmc /dev/block/mmcblk0p12 /system
cp /sdcard/app/* /system/app/
cp /sdcard/framework/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t emmc /dev/block/mmcblk0p12 /system
reboot
6.- Go to http://forum.xda-developers.com/showthread.php?t=1343807 and download Batterypercentstocklook.zip and extract services.jar and framework-res.apk and copy to sdcard/framework, then install with:
adb shell
su
stop
mount -o rw,remount -t emmc /dev/block/mmcblk0p12 /system
cp /sdcard/framework/services.jar /system/framework/
cp /sdcard/framework/framework-res.apk /system/framework/
mount -o ro,remount -t emmc /dev/block/mmcblk0p12 /system
reboot
7.- Done! You now have a Photon phone; updated, rooted, deodexed and show exact battery percent, but still locked.
Thanks.
I want move my app to /system/app/, I did follow steps under ROOT privilege
Code:
mount -o remount,rw /system /system
cat /data/local/tmp/abc.apk > /system/app/abc.apk
chmod 644 /system/app/abc.apk
mount -o remount,ro /system /system
reboot
but the abc.apk file disappear from /system/app after reboot.
if I use update.zip package under Recovery mode to write the abc.apk to /system/app, it will be normal after reboot.
so, what's the difference for wrinting system partition under Recovery mode and ROOT privilege?
Thank you very much!