Related
(DEPRECATED)
I no longer support or care to support this is someone wants to take over and deal with this and the complaints go for it. It has not been tried on the 2.2.2 version of android in case you want to try it.
Tired of all those funky ways of rooting? Wanna just push a button and be rooted?
Guess what I've got something for you.
Introducing FastbootRoot (patent not pending) for the virgin mobile optimus v
FastbootRoot was designed with simplicity in mind. The easy to use ui makes rooting your lg optimus easy and quick without all those adb commands. It takes the guess work out ( is this right, what does he mean by that? ) of rooting your phone.
Features:
flash a custom recovery
this feature only flashes a custom recovery without rooting your phone giving you the ability to back up your current system without root. I put this in here in case of needing to return the phone for warranty matters
flash the entire shebang
This flashes a new boot image, a new system image*, and custom recovery.
Revert to stock
thanks to destundead we now have the stock system image and boot combined with my stock recovery we are good to go
New experimental install windows xp fastboot drivers
My goal is to fully automate this process and to make this as painless as possible for the new users. This new feature is untested and will either work or it won't. Give me some feedback if it does or doesn't.
--------------------------How to Use--------------------------
Download fastbootroot from here and place it on your desktop.
Download the usb drivers from here
On your phone turn on usb debugging by pushing menu, then settings, then applications, then development, and then usb debugging.
Install the drivers ( I find that rebooting after the drivers have been installed will install a whole new set of drivers. I recommend this method)
unzip fastbootroot and inside double click the fastbootroot file. Make your selection and your done.
Here's a video on using it and a little explanation
watch it here
WHAT THE FUTURE HOLDS:
no need to install usb drivers
Enjoy this and remember this works fully on windows 7 and I tested it myself. No matter what there's always room for user error though in which case I take no responsibility if things go wrong.
PROBLEMS AND COMPLAINTS
Some people are reporting problems like drivers not installing or other things. First off if you have a problem you need to state exactly what operating system you are using (windows 7, windows vista, or windows xp).
This only works with the virgin mobile optimus v. Make sure you have the virgin mobile optimus v (not a optimus t, m or a picture of the v pasted on top of a w490)
Tell me what you did exactly don't lie. I know from experience when someone says, 'I did this I definitely didn't do that', whether or not they are holding something back. The more info you can give the better if your holding something back that's gonna delay the process.
This is free. I ask for donations but they aren't required at all. So when your asking for more things remember this is free.
Like my work donate to me herehttps://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=FEP8NQ8J49MX8
*the new system image is stock with root, flash_image and busybox installed
It's fully automated?
Sent from my VM670 using XDA App
overthinkingme said:
It's fully automated?
Sent from my VM670 using XDA App
Click to expand...
Click to collapse
yep the only thing that you gotta do is download fastbootroot and the lg drivers. It will take care of everything else for you. I will say that I've tested this and my earlier variant of it quite a few times. I even made a video for the other one.
Downloading this now. will give it a try. Thanks!
--bornagainpenguin
This is for lg optimus v for virgin mobile, right?
Sent from my SGH-T959 using Tapatalk
i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks
shaynes vibrant said:
i get a write error suspended reset port change on my phone when trying to run this? it says waiting on device on the fast boot system? any ideas what im doin wrong thanks
Click to expand...
Click to collapse
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good
Asadullah said:
your in fastboot by now you should be good unless you did something crazy. What will happen is windows will automatically install the fastboot drivers and do it's thing and you'll be good
Click to expand...
Click to collapse
This does not seem to be happening. How can I abort the fastboot procedure so I can reboot and try again?
--bornagainpenguin
Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin
If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Would op mind posting the manual way to root through fast boot?
Sent from my VM670 using XDA App
bornagainpenguin said:
Hello? Please someone be there who can help me!
The detection sequence you describe did not work, Windows is not finding the drivers properly. Is it safe to reboot the machine while in fastboot? Can I unplug the USB without bricking my phone?
--bornagainpenguin
Click to expand...
Click to collapse
yes your okay to unplug your phone the process either works all the way or not at all I'm confused as to why it didn't install the drivers though. I guess I'll just have to add them to the batch
overthinkingme said:
If nothing has flashed, I'm sure you're fine. It dependant on how far it got .
Click to expand...
Click to collapse
How do I know?
Right now the screen says:
Code:
Fastboot mode started
gpio_12c: invalid khz: 0
b1: i2c write error
udc_start()
-- suspend --
--reset --
-- portchange --
-- reset --
-- portchange --
STALL GET_DESCRIPTOR 128 6 1006 0 18
-- reset --
-- portchange --
-- reset --
-- portchange --
I removed the battery and the phone restarted without issues. Not sure why things did not go the way they're supposed to--could it be because I had the drivers from the ROMTOOLS package installed before? NOTE: Prior to trying this procedure I uninstalled all of those and rebooted before installing the drivers linked here.
Another thought, OP says he is running Windows Seven; I am on Windows XP. Could this have anything to do with my trouble?
--bornagainpenguin
UPDATE: I tried installing the drivers included with the ROMTOOLS package and my phone was recognized again. No luck when trying to run fastboot. Not sure why this is happening or why I am unable to use the drivers OP linked to. They seem to install when clicked but the system doesn't seem to think the drivers apply to this phone for some reason...
Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers.
I wrote this while before your last post yes there is a problem with windows xp. It doesn't download them like it would on windows 7. I can test all day long on windows 7 but not on xp. The method in the video should work for xp users
Asadullah said:
Okay what happened was your fastboot drivers didn't install correctly I'm in the process of uploading a video to show you how to install the fastboot drivers
Click to expand...
Click to collapse
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin
bornagainpenguin said:
I appreciate the effort, but unless the video is closed captioned it may not do me much good. I am hard of hearing (one of the reasons why I picked this phone was its high T4 rating which works well with my hearing aids and telecoil adapter --think headphones for hard of hearing people) so cannot always hear audio on videos very good.
--bornagainpenguin
Click to expand...
Click to collapse
It's recorded in 780 hd using camstasia. Even if you can't hear it you'll be able to follow along the process is very simple
http://www.youtube.com/watch?v=aTE30yd-P_U
here's the video
I've integrated the fastboot drivers into the next release for windows xp I need a beta tester before I release this.
Does this just root our existing system, or does it install a whole new rooted image (requiring us to reinstall all of our programs and settings)?
I have XP, by the way. If it just roots, I would be willing to beta test (but if it doesn't work, if it doesn't work, I want to be able to get back to where I was as my phone works well).
This is F*****KIN GREAT!!!! Thanks!!
I'm having bootloop issues and I see a post here which suggests that one way to fix the situation is with fastboot. Do you know if fastboot can help me? If so, how?
--bornagainpenguin
I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have
Click to expand...
Click to collapse
My computer recognizes the phone, that's not the problem. It's purely the program, I can't run it. It doesn't open.
i see try older versions of the program try googling lg flash tool do you have the megalock.dll
---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------
im sorry i just really read in full i had the issue to when i upgraded to win 10 i ended up going back to win 7 too things just wernt going well with 10 also had trouble with flash tool always failing never restoreing i was a pain i thought i messed my phone up and it ended up bein win 10 my pc has the secure boot and crap on it it even makes it a pain to dual boot ubuntu up so i just run 2 machines on my tv
A Possible Solution
alwaysdiving said:
I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.
Click to expand...
Click to collapse
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.
Abort said:
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.
Click to expand...
Click to collapse
Thanks, but I tried that already. Didn't work. In the end I transferred everything to my wife's Windows 7 computer and and did the flashing there. Everything ran as smooth as can be.
Running the Community build. Bone stock. No root. Stock recovery. No mods at all. Has taken every OTA to day without issue.
The new one just came out today, and it downloads it fine, reboots to install it, and just goes to Recovery. Doesn't install anything. I try to tell it to install from a file, point it to the update that was downloaded, instantly fails.
I try to sideload through ADB, but my PC will not see it in Recovery mode. I had this issue months ago, it has to do with the Win10 driver, but for some reason I can't recall how I fixed it.
Anyone have any ideas?
I would just skip the update, but battery life has been atrocious since the last one and I am hoping that this would fix it.
SquireSCA said:
Running the Community build. Bone stock. No root. Stock recovery. No mods at all. Has taken every OTA to day without issue.
The new one just came out today, and it downloads it fine, reboots to install it, and just goes to Recovery. Doesn't install anything. I try to tell it to install from a file, point it to the update that was downloaded, instantly fails.
I try to sideload through ADB, but my PC will not see it in Recovery mode. I had this issue months ago, it has to do with the Win10 driver, but for some reason I can't recall how I fixed it.
Anyone have any ideas?
I would just skip the update, but battery life has been atrocious since the last one and I am hoping that this would fix it.
Click to expand...
Click to collapse
Battery life has not much to do with the rom.. More with apps. So your phone does not show up under ADB? Well to the unbrick tool follow the first few steps to get your device shown up as something else in Device Manager. Don't actually use the unbrick tool just the drivers! It is required to boot windows 10 into driver signature enforcement before you change/update the driver to the one on the thread.
Puddi_Puddin said:
Battery life has not much to do with the rom.. More with apps. So your phone does not show up under ADB? Well to the unbrick tool follow the first few steps to get your device shown up as something else in Device Manager. Don't actually use the unbrick tool just the drivers! It is required to boot windows 10 into driver signature enforcement before you change/update the driver to the one on the thread.
Click to expand...
Click to collapse
Yeah, I just figured it all out a little while ago... Part of it was that Windows keeps installing the wrong drivers for ADB, and also I needed a newer version of ADB that can handle larger file size updates.
Edit Preface: Using AOSP ROM, Rooted, and phone works fine. Just below issues.
Are we just supposed to flash partition backups from payload? Cant even MSM. MSM tool and computer pickup device (QDL device in device manager) but won't start handshake. Any thoughts?
You're supposed to use MSM only when going back to stock ROM. No other way around. Also, install proper drivers and it will work just fine.
ekin_strops said:
You're supposed to use MSM only when going back to stock ROM. No other way around. Also, install proper drivers and it will work just fine.
Click to expand...
Click to collapse
I guess I worded that wrong. I'm currently on xtended trying to go back to stock. Installed all drivers, switched cables, installed newest platform tools, nada worked.
Zeus0fyork said:
I guess I worded that wrong. I'm currently on xtended trying to go back to stock. Installed all drivers, switched cables, installed newest platform tools, nada worked.
Click to expand...
Click to collapse
What platform are you talking about? Again, you can only go back to stock with MSM, and if it's for some reason failing, I can only imagine that your drivers are not correctly installed.
Hello,
I have a OnePlus 8 Pro device that has been stuck at version IN2023_11_C.21 for some time.
I've seen versions up to C33 come out, but never received them.
If I remember correctly, I upgraded from Android 11 to 12, via Oxygen Updater.
Now, on this app it tells me that setting the device as EU is wrong: I have to put INDIA, but I bought it from the official EU store.
So I'm quite confused and I would like to bring my device back to an official rom, then hoping for the update to 13.
I've read a few conversations, but there are a lot of procedures and I haven't figured out which one is the most correct to do.
Thanks for the replies.
greypilgrim said:
Hello,
I have a OnePlus 8 Pro device that has been stuck at version IN2023_11_C.21 for some time.
I've seen versions up to C33 come out, but never received them.
If I remember correctly, I upgraded from Android 11 to 12, via Oxygen Updater.
Now, on this app it tells me that setting the device as EU is wrong: I have to put INDIA, but I bought it from the official EU store.
So I'm quite confused and I would like to bring my device back to an official rom, then hoping for the update to 13.
I've read a few conversations, but there are a lot of procedures and I haven't figured out which one is the most correct to do.
Thanks for the replies.
Click to expand...
Click to collapse
The best way to clean up your phone is the MSM program.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
HolyHog said:
The best way to clean up your phone is the MSM program.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks, I've tryed... but It seem that doesn't work..
greypilgrim said:
Thanks, I've tryed... but It seem that doesn't work..
Click to expand...
Click to collapse
Make sure all your computer drivers are up to date including the optional ones.
Don't try to get in EDL mode. Start MSM and hit the start button so it will be looking for your phone. Plug it in to your computer and hold down volume up + volume down and the power key. It can be off or on when you start this. It should grab hold and start installing and then let go of the buttons. When you hard reset from an phone that's on, it puts in EDL mode automatically.
HolyHog said:
Make sure all your computer drivers are up to date including the optional ones.
Don't try to get in EDL mode. Start MSM and hit the start button so it will be looking for your phone. Plug it in to your computer and hold down volume up + volume down and the power key. It can be off or on when you start this. It should grab hold and start installing and then let go of the buttons. When you hard reset from an phone that's on, it puts in EDL mode automatically.
Click to expand...
Click to collapse
I've tryed as you said, but msn still has "param preload fail" . I'm tryng to use the package instantnoodlep_15_E.34_210201.
greypilgrim said:
I've tryed as you said, but msn still has "param preload fail" . I'm tryng to use the package instantnoodlep_15_E.34_210201.
Click to expand...
Click to collapse
That Param preload fail error cause you don't have the qualcomm driver. Check the MSM page for the download.
greypilgrim said:
Hello,
I have a OnePlus 8 Pro device that has been stuck at version IN2023_11_C.21 for some time.
I've seen versions up to C33 come out, but never received them.
If I remember correctly, I upgraded from Android 11 to 12, via Oxygen Updater.
Now, on this app it tells me that setting the device as EU is wrong: I have to put INDIA, but I bought it from the official EU store.
So I'm quite confused and I would like to bring my device back to an official rom, then hoping for the update to 13.
I've read a few conversations, but there are a lot of procedures and I haven't figured out which one is the most correct to do.
Thanks for the replies.
Click to expand...
Click to collapse
There is a comment somewehere that says u have to mod of a newer rom a txt...
I think that's your solution. If u know the exact odel u have (and region) use oxygen updated to download the correct rom
Inside zip file (I open it in 7zip) open "payload_properties.txt" in Notepad and change one line from:
oplus_update_engine_verify_disable=0
to:
oplus_update_engine_verify_disable=1
And save it - I do it at computer so 7zip repack only this changed file.
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com
I am sure there is an xda link for this, but it is the same thing...
Jimger is right, one addition. Don't extract payload_properties file, but rather edit it in archive. Idk why, but only editing file while being in archive works for me. Additionally you MUST have OPLocalUpdateForAndroid12.apk to make it work. When i was on OOS12 i installed beta 2 of OOS13 this method, then upgraded to Global OOS 13 when it was out, then yesterday i flashed EU version (sincerely i don't see any difference, only for some reason in IN build i got... VoLTE somehow), so now i'm at OOS13 EU.
ShadoV90 said:
Jimger is right, one addition. Don't extract payload_properties file, but rather edit it in archive. Idk why, but only editing file while being in archive works for me. Additionally you MUST have OPLocalUpdateForAndroid12.apk to make it work. When i was on OOS12 i installed beta 2 of OOS13 this method, then upgraded to Global OOS 13 when it was out, then yesterday i flashed EU version (sincerely i don't see any difference, only for some reason in IN build i got... VoLTE somehow), so now i'm at OOS13 EU.
Click to expand...
Click to collapse
So, I've to download oo13 from op, edit that file and instal? Let's try!