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

Root LG Optimus V Bricked?

im not trying to be rude in anyway or anything but is there any possible way we could speed this up a little? i have been up all night trying to fix it and im tired but i dont want to go to sleep until its fixed do you possibly know how long this will take?
 
im not trying to be rude in anyway at all but is there anyway we can possibly speed this up? i havnt slept all night trying to fix this and i dont wanna go to sleep until its fixed... do you possibly know how long this will take?
 
You have an S screen and drivers which is why the recovery, which was designed for the V screen and drivers, didn't work.
 
The S used the Hitachi screen, the V used to use the Novatek screen. Now it uses the Hitachi screen.
 
Once you get the Xionia v1.2518.6 on the sd card you can rename it to recovery.img if you want. Just makes it easier to type in without mistakes in the command prompt.
 
whn i put it on my sd card it put diff selections on it one was the xionia and the other is stockopv-1 is that ok? and do i put the flash image and those two things into a folder or no? and if i dont do i put it into my phone and try to do the rcovery?
 
Your flash image put unzipped near the bottom of the list of folders. Put the recovery, unzipped and renamed, in the same place . These cannot go in any folder.
 
Put the card back in the phone. Then take out battery and hold power button down for 30se .
Reinstall battery and power up phone. Then plug into PC and type in:
cd..
cd..
You should be in the root of your C drive.
Then type in: cd and then the path to your adb.exe
 
If you get the sdk folder followed by a > then type in adb shell
You should get a #
 
Ok plug it in and make sure it's fully charged first. Holler at us when it's fully charged.
 
ok i got it plugged in then i got to abd on the command prompt and it said alot of stuff kinda like the help command just says more commands
 
i typed adb shell it said *daemon not running. starting it now on port 5037 *daemon started successfully * then it said error: device not found
 
Sorry thought it take you a while to charge it. Was doing some things much needed.
please try to explain what you typed in and what you got each time you hit the enter key after each line of code.
 
i typed cd program files and hit enter, did cd.. all the way to the folder adb.exe is in then just hit adb.. then hit adb shell and thats when it said daemon starting etc..
 
Here's your problem. When you installed the wrong recovery and got the black screen it could have been fixed. But when you did a factory reset from the privacy menu with a rooted phone it borked your ROM. This could have been fixed if you had a working custom recovery. But you don't have a working custom recovery.

The only chance was if the pc recognized the phone and you could flash a new recovery with ADB commands. If it only recognizes the phone in emergency mode you have a brick.

The only other thing that can be done with it now is to crame the S firmware into it.
The only thing the phone will be able to do then is WiFi. No 3G or text or phone. Except VOIP calls
 
You must log in or register to reply here.
Back
Top Bottom