Root Do not Factory Reset your Rooted Phone

[nijel]

You should point to/select "c:\sdk\platform-tools" folder where adb.exe and aapt.exe are located.
Shell is seventh button from top on left.

 

[lumberjackegg]

okay now im in the "QtADB - Your android manager" i clicked the shell option and its says "QtADB shell. Type 'qtadb-help' for instructions" and "$"

 

[nijel]

You don't have root access, so we have to do this with fastboot.
From the Menu bar on top choose Tools->Adb->Reboot bootloader. Your phone should reboot to fastboot screen and QtADB should switch to "Fastboot" screen(press "Refresh" if it doesn't). Press "Flash recovery" button, choose your recovery img file and new recovery will be flashed. From the Menu bar on top choose Tools->Fastboot->Power off. Boot to recovery holding vol_down + home + power keys and release them at LG splash. If recovery is OK, proceed with ROM install.

 

[lumberjackegg]

but i do have root access? and reboot bootloader isnt working, plus where is the refresh button?

 

[AndyOpie150]

You broke Root access when you factory reset from the privacy menu.
nijel is an expert with QtADB, It would be a really good idea to listen to what he has to say. He knows way more than me when it comes to QtADB.
This is going to be your only hope of getting your phone straightened out. Your going to need to get a custom recovery on your phone so you can install a working ROM. Then we will work on getting you Root access again.
I've been helping people fix there mistakes for a long time now, members like nijel are hard to come by. You are getting the best advice for your problem.

 

[lumberjackegg]

oh i didn't know.. sorry. :I well im honored to be getting help from nijel and you and anyone else who is willing to help. I will listen to what you gotta say.

 

[AndyOpie150]

It's OK. I've been in your shoes and was so stressed out it almost made me sick. Then I came here and was given more help, and felt like they really cared.
We help for free because we really care. We put in countless man hours just to help, because we care.
Your in good hands, if there is a way to get your phone back to life, we'll find it.

Hitting the factory reset from the privacy menu on a rooted V usually spell B.R.I.C.K
The QtADB utility has been improved by nijel for the V and looks to be the best way to fix your problem. Getting a working custom recovery installed is going to be the key.

EDIT: One quick question. What is your phones OS version, 2.2.1 or 2.2.2. This will determine what recovery's you can or can't put on your phone, as well as what ROM's you can or can't use.

 

[nijel]

oh i didn't know.. sorry. :I well im honored to be getting help from nijel and you and anyone else who is willing to help. I will listen to what you gotta say.

So you don't have root, you don't have custom recovery and you can't boot to bootloader(fastboot).
But you can boot to Android OS and you can see/browse files with QtADB.
Correct?

Do you get message "adbd cannot run as root in production builds... bla-bla-bla" when you start QtADB?

 

[AndyOpie150]

Hey nijel, I found the download link from the old fasbootroot tutorial and it still works(downloaded a fastbootroot.zip just to make sure). Maybe this info will help? Maybe we could get lumberjackegg rooted first?

 

[nijel]

There is no other way, we need root if we don't have fastboot. I was thinking manual root copying su and Superuser.apk, but I doubt we can do anything in /system without root so probably wont work.
What is this fastbootroot.zip?

You mean this? http://forum.xda-developers.com/showthread.php?t=1031110

 

[AndyOpie150]

It was put together to allow for rooting in the fastboot bootloader screen.

 

[nijel]

It just does what we are trying to do with fastboot but he can't get to bootloader so it wont work.

:flashrecovery
cd tools
adb reboot bootloader
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot 
goto start

 

[AndyOpie150]

Duh! Brain dead, wrong thread. Now I remember where I'm at. It still will come in handy with memar's problem though (which is where I must have thought I was). Time to go to bed, night night ya'll

 

[lumberjackegg]

i believe i have 2.2.1. I don't know what booting to Android OS means but i can see/browse files. And I did not get that message when i oped up QtADB.

 

[nijel]

It means you are booting to your ROM, not to recovery.
But I'm a little confused. You are getting no root sign in shell but you did not get no root message from QtADB.
So try flashing recovery then and see how it goes.
http://androidforums.com/optimus-v-...-i-unbrick-lg-optums-v-qtabd.html#post4163766

 

[lumberjackegg]

where can i get a good recovery img?

 

[nijel]

http://androidforums.com/optimus-v-...l-things-root-guide-updated-04-01-2012-a.html

 

[sammyz]

Idk where this thread has gone, can't read everything I don't have time, but if you are stuck in fastboot first do fastboot erase recovery and then do fastboot flash recovery /recovery.img

 

[Blabah]

the Xionia_CWMA_12518.4_VM_Recovery.zip mediafire link seems to be broken. Can anybody reupload the file? thanks

 

[AndyOpie150]

Check the All Things Root Guide sticky. I put a link to a compilation of recovery.zip's in their. One of those zip's is the Xionia v1.2518.4
I'll see what I can do about having the OP know about the broken link.

 

[nickmahuta]

ok so im stuck in a bootloop with the clockworkmod recovery v3.2.0.1 so what i would have to do is flash xionia_cwma_12518.6.img to fix the bootloop problem?
i have tried to flash it but i, really new to all of this and need a lot of help trying to fix this.
when i try to flash i either get eroor oping .img or invalid argument.
what should i do?

 

[jcubslife]

Hey all. I am new to all this awesomeness! Been using a rooted Optimus V for the last couple of months and recently decided to get a triumph. Tried to restore my phone (older version 2.2.1) to original settings, thought I was done, factory reset the phone, and then bad things started to happen. I realize now that I did not properly restore my recovery. Initially had me stuck in CWM. Tried reinstalling my stock recovery and harmonia 2 to no avail. Found this thread and attempted to install xionia. When I restarted, my phone went to the factory recovery, wiping everything and then started to boot harmonia. I thought I had licked it, but now everytime I restart the phone it wipes the memory and boots harmonia as if it were a fresh install. I know I probably did a lot of things wrong, but if there is a fix somewhere, that would be awesome! Thanks to all!

 

[AndyOpie150]

ok so im stuck in a bootloop with the clockworkmod recovery v3.2.0.1 so what i would have to do is flash xionia_cwma_12518.6.img to fix the bootloop problem?
i have tried to flash it but i, really new to all of this and need a lot of help trying to fix this.
when i try to flash i either get eroor oping .img or invalid argument.
what should i do?

You need to use the .zip version of the Recovery, not the .img file. Make sure it is not in any folder (take it out of the downloads folder), put it on the root of the sd card. It can be found in the list of recovery's in the All Things Root Guide sticky. If it still doesn't work it could be you need to reformat your SD card. Pull it out and put it in a PC. Move all the contents into a new folder. Go to Start/Computer/right click on the sd card. Select format. Select format to default settings. This will take up to 10 min or more. When it is done download and put on the SD card the Xionia recovery.zip also the ROM,zip (and Gapps.zip if necessary). Go to the Recovery menu and select the recovery.zip from the "install zip from sd card option" once it's done select the "Boot into recovery option" in the advanced section. This will boot you into the Xionia recovery. Go to the advanced section and select the "fix recovery loop" option. Once done do a complete wipe and format and install the ROM (and gapps if necessary).
Note: If it's a gingerbread ROM you will need to completely wipe and format 3 times before installing the ROM when using the Xionia recovery. Once you have the ROM installed and rebooted several times you can then install the VM670NH_recovery.img though a terminal emilator on the phone. This is the best recovery for the Gingerbread ROM's at this time, but the Green recovery will be better shortly, just as soon as the dev. gets finished fixing little bugs and improving even more on the recovery concept.

 

[AndyOpie150]

Hey all. I am new to all this awesomeness! Been using a rooted Optimus V for the last couple of months and recently decided to get a triumph. Tried to restore my phone (older version 2.2.1) to original settings, thought I was done, factory reset the phone, and then bad things started to happen. I realize now that I did not properly restore my recovery. Initially had me stuck in CWM. Tried reinstalling my stock recovery and harmonia 2 to no avail. Found this thread and attempted to install xionia. When I restarted, my phone went to the factory recovery, wiping everything and then started to boot harmonia. I thought I had licked it, but now everytime I restart the phone it wipes the memory and boots harmonia as if it were a fresh install. I know I probably did a lot of things wrong, but if there is a fix somewhere, that would be awesome! Thanks to all!

If it boots into Harmonia, and the ROM is fully functional, just go Here http://androidforums.com/optimus-v-...-flash-zv9-update-technically-challenged.html This will totally return your phone to stock. Stock ROM, stock recovery, and no root.

 

[AmethystDragon]

Didn't know my phone was rooted when I bought it from a friend, performed a factory reset from the Privacy menu not knowing I shouldn't have, and now I'm stuck in the thunderrc system recovery. I'm supposed to be sending the phone in after warrantying the phone and receiving a replacement. Replacement showed up today, so I have a week or so to fix this problem.

While the steps seem simple enough, the link for the Xionia v1.2518.4 recovery is broken. The only links I can find in the All Things Root sticky are also broken (unless I'm looking in the wrong place). Can anyone help?

And afterwards, what can I do to ensure Virgin Mobile can't deny my warranty because the phone was rooted? Will there be any evidence once the system is recovered? I know VM is big on the whole Anti-rooting platform.