• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root The Truth About ROM Manager

AndyOpie150 said:
Ok Run the first line, skip the secound line, run the rest
Click to expand...

Ran command: adb shell strings /dev/mtd/mtd8 and it went back to the command line folder with no error
Then skipped 2nd command and went to 3rd command: adb reboot recovery
No error was shown but the phone screen never went to the LG screen or anything.
I'm not clear how long the reboot should take while the phone is in this state (does not seem to be rebooting or doing anything as the screen stays blank for several minutes though).

Just to see if anything else could be run tried the next group of commands:

Command: adb shell mount /dev/block/mmcblk0p1 /sdcard which did not show any error.
Since I have no idea how long a mount would take I waited about 2 minutes here.
I then tried the next command: adb push xionia_cwma_125186.img /sdcard/ only to fail with:
cannot stat 'xionia_cwma_125186.img': No such file or directory

I assume it did not mount because of the earlier command: adb reboot recovery not loading back to the command line folder which seems to usually indicate the command worked unless an error is given.

UPDATE:
Ran command: adb devices It shows:
List of devices attached
A10000199FA4A3 recovery

So I can try the process of pulling the battery, then holding power button down 30 sec. Reinstall battery, and turn power on. To then try commands once again.
Or perhaps this means I did not give the phone enough time when it was on a blank screen after running the command: adb reboot recovery

2nd UPDATE:
Tried the process of pulling the battery, then holding power button down 30 sec. Reinstalled battery, and turned power on. I then tried the commands once again.

When using command: adb shell strings /dev/mtd/mtd8
I found when monitoring more closely what seems to not give the error: device not found

I had to wait until it started to load into the BACKside-IHO screen (smaller Android icon will be in lower right corner and the text for BACKside-IHO is shown) then the command seems to run.

Then even if it made it to the following load screen with green Android, and the spinning circle the command: adb reboot recovery would seem to run with no issue
After waiting 5 minutes the phone is still on the blank screen though.

Without touching the phone battery to force restarting etc. found once again the command:
adb devices shows:
List of devices attached
A10000199FA4A3 recovery
 
Try sklpping the first two lines.
If that doesn't work, download and set up screen cast on pc.
Download newest BACKside ROM and gapps.
Download VM670NH recovery. Put ROM and gapps and recovery on root of sd card.
ROM and recovery install instructions can be found here http://androidforums.com/optimus-v-...tory-reset-your-rooted-phone.html#post3263770 read this thru twice before attempting anything.

Your going to use your pc screen to see what should be on your phones recovery menu.
up/down=volume rocker; select is the camera button.
After you get the ROM installed and rebooted twice download a terminal emulator from the market and install the proper recovery.
Okie Dokie?
 
AndyOpie150 said:
Try sklpping the first two lines.
Click to expand...


Ok, I tried the process of pulling the battery, then holding power button down 30 sec. Reinstall battery, and turn power on.

To then try only command: adb reboot recovery

The LG icon appears briefly, and now it is back on the blank screen with nothing being shown after several minutes. Does that means a successful reboot perhaps where I should now move onto the next command group for command:
adb shell mount /dev/block/mmcblk0p1 /sdcard and so on?

After waiting several minutes if I run command: adb devices It shows:
List of devices attached
A10000199FA4A3 recovery

I have not tried using the command: adb shell mount..... etc. ones at all yet.
 
AndyOpie150 said:
Finish the rest of the code yes.
Click to expand...

Ok I started command: adb shell mount /dev/block/mmcblk0p1 /sdcard

It went back to the command folder prompt indicating it ran with no issue.

I was not sure if I should wait before running next command since I was not sure if it was still mounting or not. I seem to remember when I had run this command earlier (before finding out earlier commands were an issue most likely), and tried to run the next one it gave some error about there being a process still running.
So I waited over 5 minutes or so before loading into the
command: adb push xionia_cwma_125186.img /sdcard/

It failed to run stating: cannot stat 'xionia_cwma_125186.img': No such file or directory

Perhaps I should try a different recovery .img file or..?
 
Are you typing in the recovery right? Xionia_cwma_1.2518.6 ......etc. If you are then,No,go to post 52 ^. Thats your best option now
 
AndyOpie150 said:
Are you typing in the recovery right? Xionia_cwma_1.2518.6 ......etc. If you are then,No,go to post 52 ^. Thats your best option now
Click to expand...

Basically I started back with post 52, and as I got into the phone recovery options I started running thru Installing from another ROM steps per:

http://androidforums.com/optimus-v-...wip-backside-rom-cm7-green-machine-theme.html

If you Google search for: screencast android

androidscreencast is first result found as linked here:
http://code.google.com/p/androidscreencast/

Steps 1 thru 3 were pretty easy to follow.

On Step 4 I clicked on the link there. Selected to Run it on the popup window, and it shows a Java security warning (I'm using Win 7) that I accepted. A little separate command console window appears too if needed for reference. It should open a new popup window in which the phone's screen should later appear.
In one command prompt I used it to run the adb devices command until I got response I needed:
List of devices attached
A1000 and so on device needs to be shown

Then in a second command prompt window for this androidscreencast Javasoftware I used command: javas

Then once the popup window for the phone's screen appeared I went back to the adb window to run command:
adb reboot recovery

Then it shows the ClockworkMod Recovery v3.2.0.1 on the window on computer. In working with it earlier it would even function to run things when the phone screen was shown stuck on that Android icon with spinning circle. Please see below for a screenshot:


androidscreencastadbrebootrecoveryscreenshot.jpg



I will edit this post if needed, but tried to list what I did step by step best to my knowledge.
　
You all are an **outstanding** resource that I was lucky enough to find since this is the first week I ever had the phone. Thank you very much.
 
So I rooted my phone ....great .....next I bought ROM manager premium ....you see I wanted the cyanogenmod deal ....anyways I did it as I thought I was supposed to ....and no I fail at all things techie....so now it has some of the cyanogenmod things like i can go to the settings for it but it is not it aaand now the premium version of rom manager is gone along with the market and many other things ....and when i tru to reboot into recovery mode my buttons will not let me choose anything!!!! I have to take out the battery an restart my phone to even get out of that screen .....any ideas???? sorry if I am in the wrong place didn't know where to go oh and also it keeps shutting me out with errors like cannot parse package and shutting down rom manager
 
ROM Manager did not allow for a clean install by wiping and formatting everything necessary.
Go back into your recovery and restore your backup. Put a good Gingerbread IHO ROM and the gapps on the sd card. Manually install/flash. If you forgot to make a back up you will need to turn phone off and pull sd card and put ROM and Gapps an sd card from your PC.
Hold home+volume down,then power(all at the same time). When you see the LG logo you can let go. Follow the install instructions.

All the info you need is here http://androidforums.com/optimus-v-...tory-reset-your-rooted-phone.html#post3263770

This will fix you right up.
 
Okay, so I am a little confused now after having read about ROM Manager in this thread.

I rooted my V with gingerbreak back in January and installed Rom Manager(Looks like v4.8.0.7) to install CWM Recovery. It never was able to get it to install so I ended up putting the recovery on my SD card and using the Terminal Emulator app to code it in manually which worked. Later I flashed IHO and have been using it ever since.

It's been so long that I have no idea if ROM Manager is even necessary on my phone because I only used it once to try and get CWM. Is it advisable to remove it?
 
It can manage you backups. Rename, delete, and restore them. I'm going to add a link to obijohn's Update_Wiper_1.3.zip which will make it possible to wipe everything good enough to install any ROM from it if you have the Preimium version. Fix permission works etc, etc.
 
Everything it can and cannot do is in the first post. With the exception of two Froyo ROM's and a script tweak. These will be added when I get caught up with my Guide duties.
 
Please correct me if I am wrong, but won't Bobzhome latest recovery allow me to do everything ROM Manager will?

Let's say I want to upgrade to Quattrimus on my OV, which I do:

I copy the zip to the SD card.
Reboot to recovery.
Do a Backup.
Wipe most partitions except SD card.
Install Quattrimus ICS zip.
Reboot.

What am I missing? What does ROM Manager buy me?

Thanks -
 
reidi said:
Please correct me if I am wrong, but won't Bobzhome latest recovery allow me to do everything ROM Manager will?

Let's say I want to upgrade to Quattrimus on my OV, which I do:

I copy the zip to the SD card.
Reboot to recovery.
Do a Backup.
Wipe most partitions except SD card.
Install Quattrimus ICS zip.
Reboot.

What am I missing? What does ROM Manager buy me?

Thanks -
Click to expand...

You'd also need to partition you r SD card with at least a 1GB or 512MB ext2(3 or 4) partition for more app space, however, using recovery to make the partition will wipe your sdcard, so back it up first.
And you need to flash gapps of course :p
 
reidi said:
Please correct me if I am wrong, but won't Bobzhome latest recovery allow me to do everything ROM Manager will?

Let's say I want to upgrade to Quattrimus on my OV, which I do:

I copy the zip to the SD card.
Reboot to recovery.
Do a Backup.
Wipe most partitions except SD card.
Install Quattrimus ICS zip.
Reboot.

What am I missing? What does ROM Manager buy me?

Thanks -
Click to expand...
It's spelled out in the first post. The premium version isn't worth the $5.00 he want's for it.
The biggest problem is the Dev makes all this Utility's functions available to all android phones. It is not a do everything for every phone Utility, and some functions will brick some (a lot of ) phones. There is got to be a way to contact Google and inform them about it (haven't figured that out yet). If they would just look at all the forums where members are telling other members to avoid it because of it causing bricks they would see just how much damage this utility really cause's and then pull it from the PlayStore for those phones that it harms.
 
You must log in or register to reply here.
Back
Top Bottom