Okay, I've seen a few people and various threads with this problem:
1. They have a rooted Optimus V
2. they may or may not have flashed a recovery
3. they download ROM Manager and select ROM Manager's Clockwork Recovery
4. they flash a rom and reboot
5. they get stuck in a recovery loop and run around screaming.
This was me yesterday!!
What did I do, then? I downloaded the Fastbootroot tool. That got rid of the ROM Manager's CW Recovery and put in thunderc-v-1.1.0 version recovery... that looped. I tried the 1.2.0 version, which also looped, but I could flash a different recovery, finally. So I downloaded Xionia's Clockwork Recovery and THAT worked. (this next excerpt is from my androidcentral forum post)
here's exactly what I did starting from the thunderc-v-1.2.0 recovery (i'm gonna go into too much detail for other eeijits like me):
download xionia's clockwork recovery and the flash image, unzip both onto your sdcard
put your desired rom on your sdcard (zipped, omg)
get out of usb storage mode
Get ADK Tools if you don't have it (search the forum, this is the easy stuff)
Make sure you're all mounted in mounts and settings in your current recovery.
open cmd, and get into adb shell
(this next part is from zefie's post)
enter the following commands:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /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/mtdblock5 /system
# flash_image recovery /sdcard/xionia_cwma_12518.6.img
# reboot recovery
it should reboot into xionia's clockwork recovery mod
clean dalvik cache and mount everything
choose 'fix recovery loop' under ... advanced IIRC, I can't check right now as I'm reloading my stuff onto the fixed phone
after the loop's fixed, get back into recovery and load whatever ROM you fancy.
WIN!
Recovery loop from ROM mgr backup restore...tried Kiona, tried mmarz, what next?
Newb here...BUT, in my defense...I DID NOT DO AN ANDROID SYSTEM RESTORE ON MY ROOTED PHONE!! which seems to be most people's problems with boot/recovery looping. My phone is stuck in a recovery loop after restoring a Clockworkmod backup.
History: I rooted my LG Optimus V running 2.2.2 with gingerbreak a couple of months ago. Per all instructions I could find, I installed SuperUser, Rom Manager, Titanium Backup, I also have another backup by Rerware, but I can't remember the name of it. I kept the stock ROM. Everything has been working fine.
I got a 32 gig micro card for Christmas. So, as per instructions found elsewhere, I made a backup to my sd card with ROM Manager, Titanium and Rerware. I copied my sd card to my hard drive, partitioned my new sd card, and loaded the new sd card with the old sd card data. At that point everything looked fine. But the instructions said to restore from my backup which I did with clockworkmod and now I am stuck in a recovery loop.
I completed Kionia CWMA install 1..4 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed Kionia CWMA install 1..6 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed the abd shell instructions "strings/dev/mtd/mtd8" and "flash_eraseall /dev/mtd/mtd8" per mmarz but it did not fix the issue.
I have recovery access. I have ADB running.
What should I do next? Everyone else seems to be fixed with mmarz's suggestion...
Thanks to whoever is out there for any help...
rom manager is mostly no good on V and the new V screen {after sept.} gets ruined alot by rom manager, so i wouldn't use it
get a compatible recovery at the iho wiki and install
then flash the rom of your choice
if that doesn't work there is lots of help for this in the optimus v "development" section
Thanks for your reply. I just wasn't sure what I should do next and your suggestion worked perfectly. And I guess I had to get over the fact that I was going to have to restore from scratch and get over my fear of installing a custom ROM. Luckily, of all the backups I had, Titanium worked BEAUTIFULLY! I was chicken to flash a custom ROM, but I flashed IHO Harmonia and it is beautiful and has been working flawlessly ever since. I shouldn't say flawlessly, I kept getting some gapps error but I was able to look it up easily and fix it.
Live and Learn.
the latest version of rom manager in market has bug... so we can use older version search on google. And it works again
Sent from my LG-P500 using xda premium
Related
Hey there , I'm a new Lg P500 User and I am really Unclear how to flash a custom recovery mod / megatron v1 / screen lag touch fix by milk_os
About Phone
Model: LG-P500
Android Version: 2.2.2
Kernel Version: 2.6.32.9
Software Version:V10F
Rooted with Superuser using GingerBreak .
The original thread: http://forum.xda-developers.com/showthread.php?t=1044765
Also Installed with busybox from the market.
So if anyone can show me a step by step guide to how to install custom recovery mod , megatron v1 and touch screen lag fixer by milk_os. I will reward
you with $100 Singapore by PayPal.I believe in meritocracy
Links
Custom Recovery Mod:http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
Megatron V1: http://forum.xda-developers.com/showthread.php?t=870640
Touch Screen Bug: http://forum.xda-developers.com/showthread.php?t=929941
Let the hack rage begin!
Thank You.
danialrocker said:
Hey there , I'm a new Lg P500 User and I am really Unclear how to flash a custom recovery mod / megatron v1 / screen lag touch fix by milk_os
About Phone
Model: LG-P500
Android Version: 2.2.2
Kernel Version: 2.6.32.9
Software Version:V10F
Rooted with Superuser using GingerBreak .
The original thread: http://forum.xda-developers.com/showthread.php?t=1044765
Also Installed with busybox from the market.
So if anyone can show me a step by step guide to how to install custom recovery mod , megatron v1 and touch screen lag fixer by milk_os. I will reward
you with $100 Singapore by PayPal.I believe in meritocracy
Links
Custom Recovery Mod:http://androidforums.com/getitnowmarketing/221388-custom-recovery-optimus-one-p500-thunderg.html
Megatron V1: http://forum.xda-developers.com/showthread.php?t=870640
Touch Screen Bug: http://forum.xda-developers.com/showthread.php?t=929941
Let the hack rage begin!
Thank You.
Click to expand...
Click to collapse
lol luckly i live in singapore
first of all, lets start with custom recovery
1. Download the custom recovery file from here and here
2. DO NOT rename them, and put them neatly inside the ROOT of the SD CARD (that means it should be at /sdcard/ on androids
3. next, get Terminal Emulator from the market. search it.
4. Get a nice keyboard to work on for a while. you need to type A LOT
5. get titanium backup and backup everything. menu > batch
6. reboot phone.
7. Turn on phone and go to terminal and type the following
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
Click to expand...
Click to collapse
*there should be no error except at stage 5 there could be, but not always.
8. good. flash complete. now grab the megatron ROM and the lagfix. they both should be .zip . DONT OPEN IT.
9 put the two inside the root of SD card
10. go to terminal, write
su
*press enter*
reboot recovery
11. you should have a menu of things. go to flash zip or sth (you will know) w/ ur volume buttons
12. press menu and you will be able to choose the two zips. flash any of them first, and do the second afterwords.
13. YAY DONE
14. no need for bucks thanks. just press the thanks button down there. its free.
*PM or EMAIL ME IF YOU WANT FURTHER HELP*
*[email protected]*
Also, isnt 2.2.2 not rootable??
I think it has to be downgraded to 2.2 and then rooted..
Edit:
Sorry, My mistake.. Didnt realize 2.2.2 is rootable now..
2.2.2 it's now rootable
It says that "/system/etc/install-recovery.sh ": No such file or directory.
I'm sure that I placed both of the files on the root of my sdcard
Well, I guess the hardest part is getting the recovery. Well I share my method so, here we go.
What you need:
1. terminal emulator(download from market - free)
2. recovery installer(download here)
3. your ROM which is megatron(download here)
4. Touch-screen bug fix(download here)
5. Back-up all your SD contents to your PC.
-. optional: if your file explorer doesn't support unrar/unzipping, download one. but since you have a PC just use winrar.
when you have everything, lets start.
1. extract contents of "recovey_installer.rar" to the root(meaning the base) of your SDcard.(it contains 3 files, so you should also see 3 new files on your SD card).
2. open terminal emulator, enter these lines(press enter after each line):
Code:
su
sh /sdcard/rf.sh
just wait and this should reboot you directly to recovery.
3. now in recovery(remember: "vol + and - button" is "up and down" "menu button is ok/select" and "back button" is back) select options:
Partition sdcard > partition SD
4. when asked choose your desired partition size then choose swap size as 0. This should format your SD card.(initially this will leave you with an ext2 partition, if you want ext3 then upgrade it to ext3 and so on using the same menu)
5. when done, press back repeatedly and reboot.
6. now, move your ROM(megatron) and the touchscreen-lag-fix files to the root of your SD card.
7. open terminal again and enter these commands
Code:
su
reboot recovery
just wait and it should bring you back to recovery.
8. in recovery, choose option:
- flash zip menu
- to avoid hiccups just toggle the signature verification
- flash zip from sdcard
- first flash your rom(megatron), when done immediately flash touchscreen-bug-fix
- press back repeatedly then reboot.
9. enjoy
danialrocker said:
It says that "/system/etc/install-recovery.sh ": No such file or directory.
I'm sure that I placed both of the files on the root of my sdcard
Click to expand...
Click to collapse
just ignore that error message. this line is only there for those with different phone models which has the mention file in the phone internal storage. so this shouldn't affect optimus one users.
@ungaze, i did your way . It took me to android system recovery .
Anyway it didnt ask me for partition sdcard. So should i just reboot my phone?
congratulations, you now have recovery. you should see some options.
press volume buttons to navigate up and down(menu button=select/ok). Choose the option:
- Partition sdcard
- Partition SD
If you want to explore your phone a bit more, you could just reboot your phone for now. Just remember, to go back to recovery you could open terminal and enter:
Code:
su
reboot recovery
or when phone is off, press and hold "power/lock button"+"home button"+"vol down button" until recovery menu shows up.
Alright , did that . My friend told me about nandroid how can i do that before i flash the other roms ?
theres a menu option "backup/restore" open it and choose "nand backup". when done, there should be a folder in your SD named "nand" copy the contents to a pc or somewhere safe as this will serve as your backup file.
Okay, i did a nandroid and ready to flash roms . Wish me well =)
Anyway why do i receive E:Bad boot message when i reboot recovery.
everyone has it. it's perfectly fine. good luck
Anyway, as I was nandroid-ing i saw this video http://www.youtube.com/watch?v=s5GWgjJT2zo in the end, it shows the guy having no reception?
edit: He didnt have it on at the first place anyway. Sorry for the inconvenience.
i didnt view the link but im guessing hes using amon_ra v1.1, the method i gave you installs amon_ra v1.2 which fixes most bugs with ext4 and nand recovery/backup
By toggl-ing signature verification do you mean to enable or disable it?
disable. this is really not necessary as the zips youre about to apply are surely signed. but in case you have problems in the future, just remember that disabling sig veryfication may fix the problem.
Thanks man, how do i donate to you?
Btw i just screw my phone. Stuck at android screen page ;(. How do i restore the nandroid backup? Should i wipe my phone first, then do nandroid restore?
Will it restore me my version 2.2.2?
When i nandroid it , my phone was on ver 2.2.2
Ungaze?
Sent from my LG-P500 using XDA Premium App
Check your inbox
** This is only needed for those that tried to apply the update and it failed. **
So I saw a tweet from our friends at WebOS Internals that people were having issues upgrading their Touchpads to WebOS 3.0.5 with Android (CM) installed. Their suggestion was to run the Android Removal utility from PreWare and reinstall after the upgrade. I didn't want to go through a reinstall of CM so I came up with the follow instructions. It worked well for me, I hope it works for you...
** As with anything you do to your device, this is done at your own risk. **
These instructions are for Windows but you should be able to easily adapt this to your OS of choice. You will need to have Palm/HP's novacom drivers installed.
Boot the Touchpad into WebOS and attach your Touchpad to your via USB in Charge only mode.
Run ->
Code:
"C:\Program Files\Palm, Inc\terminal\novaterm.bat"
From the menu File --> Connect and Accept the little pop-up.
Run these commands at the shell prompt to create a new directory on the /media partition, copy your uImages to the /media partition, remount /boot and delete the Android related uImage files from /boot. You may have an error deleting one of the files if you don't have CWM or TWRP installed.
Code:
mkdir /media/internal/uimage
cp /boot/uImage.* /media/internal/uimage/
mount -o remount,rw /boot
rm /boot/uImage.CyanogenMod
rm /boot/uImage.ClockworkMod
rm /boot/uImage.TWRP
Do the update via the WebOS System Updates app. Once the update is complete do the following:
In NovaCom do File --> Connect again.
At the shell prompt execute the following:
Code:
mount -o remount,rw /boot
cp /media/internal/uimage/uImage.CyanogenMod /boot
cp /media/internal/uimage/uImage.ClockworkMod /boot
cp /media/internal/uimage/uImage.TWRP /boot
That should do it. Once you reboot your TouchPad you should be able to get into CM/Android.
Nice post+ I will be testing this out Tom
I updated to 3.0.5, and it would not boot back into CM7 (reboot spin), so I went into recovery mode, and re-flashed the CM7 3.5 Alpha zip file, and it all worked for me.
Just did this on my touchpad, worked like a charm. Thanks!
Thanks nice information
I updated webos and had no issues. You should probably make a nandroid beforehand just incase you have to doctor. You can always restore after you put mboot and cm back on. I have mboot 0.3.5 too.
Sent from my GT-i9100 using Tapatalk
Worked great, thx for the info
Good info!!
Thanks
Personally I upgraded before seeing this and I only removed uimage.TWRP and it worked for me. (I also uninstalled UberKernel as a precaution)
Did this and it updated it but now I can't get into moboot any suggestions?
i get read only file system on first mkdir command
can;t proceed
lvpre said:
I updated webos and had no issues. You should probably make a nandroid beforehand just incase you have to doctor. You can always restore after you put mboot and cm back on. I have mboot 0.3.5 too.
Sent from my GT-i9100 using Tapatalk
Click to expand...
Click to collapse
I guess I was one of the lucky ones too because I didn't have any problems updating webos either. I did the system update from the app in webos to go from 3.0.2 to 3.0.5 and when it was done it rebooted into webos and said the update was successful. Once I powered it off and back on moboot was intact and cm7 booted normally. This thread was my backup cause I was definitely crossing my fingers lol. Now I'm off to get alpha 2!
Followed your instructions, performed the update over CM9 a2.
All is good, thank you.
With CM9 A2 released I finally took the plunge and left CM7.
I uninstalled uberkernal in webos, used webosdoctor to upgrade to 3.0.5 without any issues, and then loaded up CM9 with the latest gapps, CWM, and moboot.
This time I really screwed up my GT7510 WiFi! I performed a format on the wrong partition without having a custom ROM on the sdcard. Stupid of course, but after some reading I'm able to push files via adb to the tab. The only thing is that I don't where to push the custom_rom.zip to, so that i can use the "apply /sdcard/update.zip"-option in CWM. I tried pushing the file for several times now, but after that I can't find it on the tab. Maybe someone can help me?
[edit] btw CWM Recovery version is 4.0.0.4
[edit 2] Fixed it by flashing stock ROM via Odin! Really nice to see some movement on the screen. First tried to flash another version of CWM but that didn't work.
I had a similar problem recently and it took me a while to figure out adb, here's how to do it for future reference:
Code:
adb shell mount /data
adb push your_rom.zip /sdcard/
/sdcard seems to mount at /data/media so you actually have to mount the /data partition to get to the sdcard. I'm running CWM 5.0.2.7 but it's probably the same for all versions.
Thanks! Will be of use the next time (hope not ).
ok, i think i played with this too much and im stuck!
have a droid xt912, was running ICS, i rooted it, saved root via voodoo, applied the JB Leak, recovered root, and installed safestrap 3.11
i went into safe strap, made a system backup, and then F'ed up... i forgot to make a new rom slot and switch to it, so i cleared out the stock system folder, and attempted to install a rom... it didnt boot, but i could still get back into safe strap...
i recovered the stock system, but it didnt fully recover.. it gets past the boot logo, makes the boot sound but doesnt boot?
i should of stopped there but didnt, and i reapplied the JB leak... now safe strap is gone, and phone doesnt boot correctly...
i can turn it on, i can still connect via ADB, and even access shell root...
figured i messed it up enough... lol... and should probably stop and look around, found the droid utility 1.82, but thats only if i was still on ICS, since my last install was JB, probably dont want to try and install anything ICS related...
looking for ideas...
ok, i was able to do wipes via stock recovery, and it now brings back up safe strap 3.11, stock rom still will not boot, but im installing a custom rom right now...
hope, i guess now that this is kinda back, how do i fix my stock rom?
You could try and get hold of a system back up from somebody running JB restore that back to stock slot..just an idea
Sent from my XT910 using xda app-developers app
This must be my issue
NOTE: - Do NOT make a backup while su is protected by VooDoo. This will cause an incomplete restore of your system and result in booting to a black screen. Remove the su backup from within VooDoo prior to creating any backup.
Going to try the following:
http://www.droidrzr.com/index.php/topic/7701-how-to-recover-the-stock-slot-on-xt912-running-jb-ota/
Sent from my MB886 using xda premium
If your problem is because of su-backup, then here is solution for you
run ss, select stock-slot, connect to computer, run adb shell
cd / && mount -t ext3 /dev/block/system /system && cd /system/
tar xf /sdcard/TWRP/BACKUPS/stock-stock-2013-01-15--07-53-10/system.ext3.win --exclude=./su-backup
cd / && umount /system
reboot
This will restore your backup without problems related to su-backup
PS: make sure you use your timestamp (stock-stock-2013-01-15--07-53-10)
This helped me out not being by a computer. Downloaded the backup. And all is good
Sent from my DROID RAZR using xda premium
Helped me recover OTA JB 98.72.16.XT912
yoyurik said:
If your problem is because of su-backup, then here is solution for you
run ss, select stock-slot, connect to computer, run adb shell
cd / && mount -t ext3 /dev/block/system /system && cd /system/
tar xf /sdcard/TWRP/BACKUPS/stock-stock-2013-01-15--07-53-10/system.ext3.win --exclude=./su-backup
cd / && umount /system
reboot
This will restore your backup without problems related to su-backup
PS: make sure you use your timestamp (stock-stock-2013-01-15--07-53-10)
Click to expand...
Click to collapse
After receiving the latest JB soak, I immediately made a safestrap 3.11 backup while root was protected with VooDoo. After messing with some system files, I decided to just do a restore back to stock. The phone booted up and hung at a black screen. I was able to restore the backup to another slot and boot from there, but not unto the stock slot.
So I tried using the above instructions using ADB to restore /system while excluding the su-backup file but got permission errors. So I decided to use 7-Zip, open system.ext3.win and delete su-backup file from there. Then copied the "new" modified backup folder to external SD, boot into safestrap 3.11 and restore that backup into the stock slot. I was pleasantly surprised that it worked!!! And I didn't lose root either!
This will teach me never to do a safestrap backup while root is protected with VooDoo.
Thank you so much for the idea! I just implemented it a bit differently when ADB didn't cooperate.
hi folks,
I installed a new Kernel on my Samsung Galaxy S plus. Its on CyanogenMod 10.1. I overclocked the default 1.4 GHz processor to 1.8 GHz. Mistakenly i set the options on the app as set on boot. Now after booting its freezing up.
I can boot in Recovery mode. Any idea how to push the stock kernel file to the SD card?
I don't have any backup ROMs or kernels on the phone. Neither is the Debugging mode on.
I don't want to do a factory reset now. Please help.
Using ADB i tried the push option
K:\ADB>adb.exe push Stock_Kernel.zip /sdcard/
this also showed that the file was pushed
1877 KB/s (3665845 bytes in 1.906s)
but there is no zip file on the sdcard
Is there anything i can do with Eclipse ?
Regards,
Anoop
[SOLVED] Phone freeze on Kernel overclocking
hi all,
This was resolved by Christopher83 whose Kernel i was testing.
Resolution steps:
1. Created a folder called ADB in my PC's K: drive
2. Copied these three files into that folder - 1. adb.exe, 2. AdbWinApi.dll and 3. AdbWinUsbApi.dll
3. Copied the stock kernel zip file there too
4. Rebooted the phone in Recovery mode
5. Connected the phone to PC(Windows) with USB cable once the Recovery screen came up
6. Waited till the two drives were seen in the Windows drive list
7. Executed the command window and typed the below in it after changing the directory to the ADB one
K:\ADB>adb.exe shell mount -t vfat -o rw /dev/block/mmcblk0p28 /sdcard
K:\ADB>adb.exe shell ls -l /sdcard/ (to see the list of files)
K:\ADB>adb.exe push Stock_Kernel.zip /sdcard/
K:\ADB>adb.exe shell ls -l /sdcard/ (again to see the list of files and to confirm that the stock zip was copied)8. Disconnected the USB
(please try to do these steps a bit faster, my Recovery screen blanked out after 2 or 3 minutes of inactivity)
9. In the Recovery mode i did the following -
a) Install zip from sdcard
b)Choose zip file and then selected the stock kernel zip and flashed it10. Wiped cache and Dalvik and fixed permission
11. Rebooted and all was fine like before (after all the apps were automatically fixed)
thanks very much, Christopher
You're welcome!
Thank you too for your patience.
Probably you are using a Recovery that is not an ADC Team recovery (this is why you have a shutdown after 2-3 minutes)... provide to update it with the Fixed ones we published (CWM or TWRP)... http://forum.xda-developers.com/showthread.php?t=2463347
In general if an OC kernel has been set to apply the OC/UV during boot (and these settings are not stable for your hardware), the easy way is to switch on the phone in recovery and flash the stock kernel that is NOT OC/UV... in this way the phone can start booting with standard frequencies/voltages... after booting, go in Performance settings and set newly the frequencies and set also the Set On Boot switch...
If you used an external app to set the OC parameters, with the stock kernel, open it and remove the Set On Boot option... in this way there is no stored values anymore... than you can reinstall OC kernel...
If you reinstall the OC kernel, I expect that the standard settings will be taken and used... an anyway be carefully with the settings... before set them on boot, be sure they do not give problems, to avoid a new booting freeze... remember that all the phones are different, so one can accept OC and UV, another not... that's life!!
Regards
Install Touch version of TWRP
smeroni68 said:
Probably you are using a Recovery that is not an ADC Team recovery (this is why you have a shutdown after 2-3 minutes)... provide to update it with the Fixed ones we published (CWM or TWRP)... http://forum.xda-developers.com/showthread.php?t=2463347
Regards
Click to expand...
Click to collapse
Smeroni, thanks for the advise. I'd like to install the touch TWRP Recovery version.
Currently i'm now on cwm6032-Build2-ariesve-alireza7991.zip.
Can i safely follow the same process as mentioned in your post, to install TWRP ?
a) Install TWRP Recovery to SD card
b) Reboot in Recovery mode
c) Soft reboot to recovery mode again
d) Select install from SD Card
e) Select TWRP file and install
f) Reboot normally
thanks much!
smeroni68 said:
anoopgkris said:
hi Smeroni, i dont know if you got my message when i quoted you on my freeze issue.
Wanted help in installing TWRP. Please see my message below.
Smeroni, thanks for the advise. I'd like to install the touch TWRP Recovery version.
Currently i'm now on cwm6032-Build2-ariesve-alireza7991.zip.
Can i safely follow the same process as mentioned in your post, to install TWRP ?
a) Install TWRP Recovery to SD card
b) Reboot in Recovery mode
c) Soft reboot to recovery mode again
d) Select install from SD Card
e) Select TWRP file and install
f) Reboot normally
thanks much!
Click to expand...
Click to collapse
Hi,
sorry but I lost your message.
Yes the procedure is nearly correct... but:
a) Copy the TWRP Recovery zip file to SD card
b) Reboot in Recovery mode (from the rom menu)
c) Soft reboot to recovery mode again (just to be sure nothing strange will happen)
d) Select install from SD Card
e) Select TWRP file and install
f) Reboot to recovery and check the new one
g) Reboot to system...
I hope I understood your PM... if not write me back.
Regards
Click to expand...
Click to collapse
Smeroni, thanks for the advise!! I'm posting it here.
Installed like a charm!
Regards,
Anoop