Hello everybody! I need help with my Moto e5 play XT1921-3 the problem that I have been facing is that the phone won't turn on like it used to. It still, charges, but I can only get it into ap fastboot mode and it does not let me access any of the features like recovery mode, because when I select it, it just turns the phone off and flashes a charging logo over and over again. I have never rooted my phone or have done anything riskful with it. It is very difficult to get it into ap fastboot with the battery inserted in the phone, but it is possible. This problem happened out of nowhere. All I did was take out the battery of my phone, after Shutting it off all the way. Then when I put the battery back in, this is when this problem started happening. This has happened to me before and I have fixed it before, using rsd lite, but now when I try to use rsd lite, I get a failed error everytime saying "failed partion gpt.bin/32" I also tried to fix that error, but I just keep getting an error after error message, I even took it to the T-Mobile store and they told me to keep it charged overnight. This is starting to get very stressful because I need my phone. If anyone can please help me, that will be very appreciated. Thank you.
greggie134 said:
Hello everybody! I need help with my Moto e5 play XT1921-3 the problem that I have been facing is that the phone won't turn on like it used to. It still, charges, but I can only get it into ap fastboot mode and it does not let me access any of the features like recovery mode, because when I select it, it just turns the phone off and flashes a charging logo over and over again. I have never rooted my phone or have done anything riskful with it. It is very difficult to get it into ap fastboot with the battery inserted in the phone, but it is possible. This problem happened out of nowhere. All I did was take out the battery of my phone, after Shutting it off all the way. Then when I put the battery back in, this is when this problem started happening. This has happened to me before and I have fixed it before, using rsd lite, but now when I try to use rsd lite, I get a failed error everytime saying "failed partion gpt.bin/32" I also tried to fix that error, but I just keep getting an error after error message, I even took it to the T-Mobile store and they told me to keep it charged overnight. This is starting to get very stressful because I need my phone. If anyone can please help me, that will be very appreciated. Thank you.
Click to expand...
Click to collapse
Use lenovo moto smart assist to flash your device, something that will fix the problem.
I tried that but lenovo smart assist does not recognize my phone And I cant get past the apfastboot screen
greggie134 said:
I tried that but lenovo smart assist does not recognize my phone And I cant get past the apfastboot screen
Click to expand...
Click to collapse
Try flashing the device using fastboot, maybe it will work.
Related
So I rooted my sister's optimus v about a month ago. Today she installed a battery mod app from applanet and as soon as she chose which battery mod she wanted she had to restart her phone for the changes to be applied, but when rebooting the phone it would only get stuck in reboot. So I tried to start it up in recovery and got the blue screen that says fastboot mode started. I looked that up online and found a fix to it but I need it to go into emergency mode to fix it that way and it will not go into emergency mode, any combination of keys only takes it to either the blue screen with the fastboot mode message or it just reboots and gets stuck. So now what do I do? I really need to find a way to fix her phone. Thanks in advance to anyone who tries to help.
try to turn on the phone & use LGMobile update tool. That should recognise the phone & install original lg fw
tabs648 said:
So I rooted my sister's optimus v about a month ago. Today she installed a battery mod app from applanet and as soon as she chose which battery mod she wanted she had to restart her phone for the changes to be applied, but when rebooting the phone it would only get stuck in reboot. So I tried to start it up in recovery and got the blue screen that says fastboot mode started. I looked that up online and found a fix to it but I need it to go into emergency mode to fix it that way and it will not go into emergency mode, any combination of keys only takes it to either the blue screen with the fastboot mode message or it just reboots and gets stuck. So now what do I do? I really need to find a way to fix her phone. Thanks in advance to anyone who tries to help.
Click to expand...
Click to collapse
give a try to error guides over here http://forum.xda-developers.com/showthread.php?t=883314 it has done wonders for many flash in cs emergency mode from the flasher menu. Read detail guide in the link provided.
I am not sure if it works for optimus v but it does works for optimus 1. give it at try
I managed to finally get the phone into emergency mode. I had installed the LG mobile support tool and installed all the drivers and tried to go that route but it kept telling me I only had one of four drivers installed, even though I have installed several drivers. After all of that I had finally got it into emergency mode so I went back to trying KDZ. I'm supposed to select the rom where it asks for the KDZ file right? But when I go to browse for the rom file it doesn't show up in the folder I put it in. I've rooted 4 phones and have done so many other things with them and never bricked one, was always able to figure out everything I did and never had to ask any questions but I can't figure this out to save my life and it is driving me crazy. I do really appreciate you guys for the suggestions and thanks to your suggestions I have gotten this far.
Hey, I have the same problem. I rooted my phone then I installed that battery mod app on applanet. I installed it then when I had to restart my phone for it to apply it just got stuck and kept looping the reboot screen where it says "ANDROID". Did you get ur fixed yet?
tabs648 said:
I managed to finally get the phone into emergency mode. I had installed the LG mobile support tool and installed all the drivers and tried to go that route but it kept telling me I only had one of four drivers installed, even though I have installed several drivers. After all of that I had finally got it into emergency mode so I went back to trying KDZ. I'm supposed to select the rom where it asks for the KDZ file right? But when I go to browse for the rom file it doesn't show up in the folder I put it in. I've rooted 4 phones and have done so many other things with them and never bricked one, was always able to figure out everything I did and never had to ask any questions but I can't figure this out to save my life and it is driving me crazy. I do really appreciate you guys for the suggestions and thanks to your suggestions I have gotten this far.
Click to expand...
Click to collapse
I'm having the same issue right now, although at least you have managed to get it into emergency mode. How did you do it?
The other issue I'm seeing is that there is no .kdz for the Optimus V LGVM670. I found a .cab file that is supposed to be the newest update, but not even sure that will work with the the kdz manager.
It was my sister's phone and I had the same problem with kdz. Had the cab file so couldn't use it with kdz. My sister left her phone with me for a few days to try to fix it and when I couldn't she took it home and managed to fully brick it to where it would do nothing at all so she had to get a new phone. I got it into emergency mode by holding down the volume and it was either the back button or the home button I pushed at the same time, can't remember which. As I held those down I plugged in the USB cord that was connected to my laptop and it went right into emergency mode. Just make sure you disable that LG modem in the device manager on the computer before doing anything because my sister forgot to do that and that is how she fully bricked her phone. Good luck to you guys and if anyone figures out how to fix it I would be interested in knowing how you did it.
tabs648 said:
It was my sister's phone and I had the same problem with kdz. Had the cab file so couldn't use it with kdz. My sister left her phone with me for a few days to try to fix it and when I couldn't she took it home and managed to fully brick it to where it would do nothing at all so she had to get a new phone. I got it into emergency mode by holding down the volume and it was either the back button or the home button I pushed at the same time, can't remember which. As I held those down I plugged in the USB cord that was connected to my laptop and it went right into emergency mode. Just make sure you disable that LG modem in the device manager on the computer before doing anything because my sister forgot to do that and that is how she fully bricked her phone. Good luck to you guys and if anyone figures out how to fix it I would be interested in knowing how you did it.
Click to expand...
Click to collapse
hmmmmm, I don't remember completely how I did it, but there was a very helpful guide floating around XDA. I bricked my Mom's Optimus one as well . I actually had to go to the LG support site, type in my Phone serial number and find a list of all the firmware available. From there I right clicked the page and got the page source. From there I got my firmware and I entered it in the KAZ or LG B2I Agent ? - Dont quite remember. Anyways, it ended up working out for me, but I accidentally flashed the German firmware, but in the end, everything was all good LOOL.
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
are you getting a screen with just...
(SVF message: 105:1:2 failed to boot 0x1000)
or something like this?
No OS detected, going to rsd mode in 5seconds press a key to stop count down available modes are:
1)rsd
2)fastboot
3)NvFlash
4)Bp HW Bypass rsd
5)BP HW bypass QC Dload
6)BP HW diag & Boot AP
7)BP HW Bypass BP only
8)BP SW Bypass RSD
9)Android recovery
10)boot android (no BP)
11)Device UID
12)console=tty50,115200n8
13 Early USB enumeration
14)BP tools
Did you not read the WARNING thread? It's stickied and is called WARNING for a reason.
[WARNING] Hard Brick with Official 4.5.91 Update
http://forum.xda-developers.com/showthread.php?t=1160408
If the error is indeed (SVF message: 105:1:2 failed to boot 0x1000), you are SoL.
Defnow...i keep getting the first msg. followed by a REALLY quick one about RSD and then the phone shuts off...to the point where i need to take the battery out so i can look at the msg again. Edgeicator was right on target with the link.
Edgeicator, you got it right...unfortunately i didn't read the post...the shock of loosing a phone like this (specially living in Brazil) was enough to have me trying everything i could...i did read a couple of posts where people was being told to try the rollback...i was stupid and unlucky...a dangerous combination.
So i guess there's no solution in sight? should i just prepare myself psychologically to buy ANOTHER phone?
Thanks for the answer guys.
hard brick man. Sorry.
Sent from my MB860 using XDA App
if u can somehow get the phone to stay on and be recognized in RSD u could try to flash the pudding sbf then fast boot and load the system and boot.img files from the fruitcakes thread. Otherwise ull be buyin a new phone if u cant get a warranty replacement.
GeekIndustries said:
Defnow...i keep getting the first msg. followed by a REALLY quick one about RSD and then the phone shuts off...to the point where i need to take the battery out so i can look at the msg again. Edgeicator was right on target with the link.
Edgeicator, you got it right...unfortunately i didn't read the post...the shock of loosing a phone like this (specially living in Brazil) was enough to have me trying everything i could...i did read a couple of posts where people was being told to try the rollback...i was stupid and unlucky...a dangerous combination.
So i guess there's no solution in sight? should i just prepare myself psychologically to buy ANOTHER phone?
Thanks for the answer guys.
Click to expand...
Click to collapse
I believe if its still under warranty you call up the ATT guys which will direct you to the Moto guys and they will ask you to ship your phone to them to fix since its a software related issue.
And how the hell do you manage to HARD BRICK your phone even with all these threads and warnings.
One question though, when you boot up the phone does the computer recognize it? I believe if it does you still can fix it.
Yeah i thought so...it sucks, but its good learning.
As i said before, searched around the web and got a couple posts, all pointing in the direction of a rollback, even if already updated to 2.3.4 ...bad luck for me.
I already sent msgs to those threads so they post a big ass red warning so no one will follow the same path.
...time to ponder my next buy...should i go for a replacement Atrix...should i try the galaxy 2s...should i get a crappy phone and wait for Atrix2?
GeekIndustries said:
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
Click to expand...
Click to collapse
Another one bites the dust...Sounds like a HARD Brick. Ginger*ucked!!
GeekIndustries said:
Hi all.
I'm in dire need of help...
I was glad to see the gingerbread update popping up on my atrix...so i got home (better internet) and did the update. Everything seemed fine until i tried to put the phone to sleep (pushed the power button). The thing just rebooted. Tried it again and the same thing happened...next time it turned on i just waited for it to go to sleep mode by itself and again it booted.
Searching the forums, the answers pointed me to the direction of a factory reset...and away i went...to no new results. It just kept on booting. So i decided to do a rollback do the previous version and that's when it got ugly. RSD gave me a FAIL in the flashing process and now i cant boot the phone.
Thing is...it gives me the black and white screen saying it couldn't boot, but as soon as the RSD mode msg shows up it just turns of. I can't get it to stay on for the usb to pick the phone up...
how am i supposed to retry to flash it again?!
ANY help would come in handy...i'm about to loose hope.
Thanks in advance!
-claudio
Click to expand...
Click to collapse
Another one bites the dust...Sounds like a HARD Brick. Ginger*ucked!!
Hi XDA, been lurking for a while and today decided to start posting, beginning with a relatively urgent question.
My brother's been marveling at the ability to flash custom ROMs onto my Galaxy S2, and decided he wanted to root his Atrix today. Rooting process went well (he used Pete's Motorola Root Tools) and then flashed CWM through ROM Manager, but did NOT unlock his bootloader. After CWM was purportedly done, he put a ROM onto his HDD, turned the phone off, and attempted to boot into CWM. He was greeted with an error message, "Failure to Boot 2, Starting RSD Mode", which pops up whether he tries to turn on the phone normally or by holding the volume button down. Taking out the battery doesn't help.
Now, my assumption is that because he didn't unlock his bootloader, he's getting this error, but my experience with Android dev is limited. So, how would I go about fixing this? My only concern is getting the phone back to a working state, we don't care about the data on it.
Thank you for the time taken to read and answer this question, any and all help is appreciated.
Warm Regards,
Leo
EDIT: Just want to make sure, I did a fair amount of searching before I made this thread and found a bunch of answers, just not sure which one I should do. One thread champions just unlocking the bootloader, others suggest flashing an OEM ROM, which I'm not sure how to do without CWM. Essentially I'm just looking for some guidance and would deeply appreciate any help I can get.
EDIT 2: Forgot to add - he was running 2.2.1 stock. Root was successful. Feel free to ask any questions if necessary.
UPDATE: I've been trying to use these instructions to unlock the bootloader, but I'm stuck on the step that asks you to reboot your phone into RSD mode. The phone doesn't boot without being plugged in, and gives me the following error when I do:
Failed to Boot 2, Starting RSD Mode
"Battery is too low to Flash". Right now the phone's plugged into the wall with this message displaying,
It also goes without saying that RSD Mode, in fact, is never started .
Added some more information (apparently new members aren't allowed to post links, so added the information as UPDATE in the original post).
Again, thanks for your help and suggestions.
Bump, somebody please weigh in.
- Leo
Sent from my i777 using Tapatalk, on ICScrweD 2.1
FatalFlaw said:
Hi XDA, been lurking for a while and today decided to start posting, beginning with a relatively urgent question.
My brother's been marveling at the ability to flash custom ROMs onto my Galaxy S2, and decided he wanted to root his Atrix today. Rooting process went well (he used Pete's Motorola Root Tools) and then flashed CWM through ROM Manager, but did NOT unlock his bootloader. After CWM was purportedly done, he put a ROM onto his HDD, turned the phone off, and attempted to boot into CWM. He was greeted with an error message, "Failure to Boot 2, Starting RSD Mode", which pops up whether he tries to turn on the phone normally or by holding the volume button down. Taking out the battery doesn't help.
Now, my assumption is that because he didn't unlock his bootloader, he's getting this error, but my experience with Android dev is limited. So, how would I go about fixing this? My only concern is getting the phone back to a working state, we don't care about the data on it.
Thank you for the time taken to read and answer this question, any and all help is appreciated.
Warm Regards,
Leo
EDIT: Just want to make sure, I did a fair amount of searching before I made this thread and found a bunch of answers, just not sure which one I should do. One thread champions just unlocking the bootloader, others suggest flashing an OEM ROM, which I'm not sure how to do without CWM. Essentially I'm just looking for some guidance and would deeply appreciate any help I can get.
EDIT 2: Forgot to add - he was running 2.2.1 stock. Root was successful. Feel free to ask any questions if necessary.
UPDATE: I've been trying to use these instructions to unlock the bootloader, but I'm stuck on the step that asks you to reboot your phone into RSD mode. The phone doesn't boot without being plugged in, and gives me the following error when I do:
Failed to Boot 2, Starting RSD Mode
"Battery is too low to Flash". Right now the phone's plugged into the wall with this message displaying,
It also goes without saying that RSD Mode, in fact, is never started .
Click to expand...
Click to collapse
You are correct in just trying to unlock the BL. Unfortunately, you will need a charged battery to do so. If you don't have access to a different battery, you can go to an AT&T store and they should charge it for you.
The OEM you're referring to is a full .sbf, instead of just the smaller "unlock" .sbf. That is an option, but in all honesty, unlocking the BL should be the quickest way to fix your situation.
If you run into any problems, let us know.
Thanks for the advice, it's immensely reassuring. He went to an AT&T store and they were unhelpful, refused to charge it for him I'm going to order a battery charger off Amazon and charge it that way, and will post here when I have results.
In the meantime if anyone else has something to add it would be quite appreciated.
Thanks,
Leo
Sent from my i777 using Tapatalk, on ICScrweD 2.1
Alright, we've run into a problem.
The screen never gets past the error message "Failure to Boot 2, Starting RSD Mode". We turn it off, hold power and up at the same time, and it still boots to that message. I press the power button and hold the volume up button, nothing changes.
The battery is charged.
Is there something I'm missing here?
FatalFlaw said:
Alright, we've run into a problem.
The screen never gets past the error message "Failure to Boot 2, Starting RSD Mode". We turn it off, hold power and up at the same time, and it still boots to that message. I press the power button and hold the volume up button, nothing changes.
The battery is charged.
Is there something I'm missing here?
Click to expand...
Click to collapse
The .sbf's are flashed while your phone is in RSD Mode
in order to charge your battery (to fix the "Battery is too low" message) you will need to sacrifice any USB cable, cut it open and tape the red and black wires to the battery. (Red goes on +, Black goes on -)
ghost_og said:
The .sbf's are flashed while your phone is in RSD Mode
Click to expand...
Click to collapse
Yep, I realized that. I thought "Starting RSD Mode" would at some point subside, and it would say something along the lines of "In RSD Mode" or something. But he flashed an unlock SBF and got it unlocked. He now has a beautiful Atrix running ICS MIUI.
Thank you all for the help.
Same problem but the solution does not work for me
I am in the same boat. I downloaded RSD 5.9 and used the file in pudding.rar. After I loaded the file, RSD said it passed with 100% load but the phone is still stuck in the same place. Can anyone help?
Just got this phone of ebay. Said it would power on but unable to get past boot up screen. They however didnt tell me there was also an error on screen. It says "Modem did not power up (3). Starting RSD protcol support." Battery too low to flash. So i went to my local radio shack to charge it on there universal charge. so i got the battery too low error to go away and my learning started from there. So i figured out what rsd was, got it and tries flashing an sbf to factory stock hoping the radio software got borked. But with no luck i keep getting the "error to switching phone to bp pass through mode". it will boot up no problem in "boot android (no bp)". so is the radio broke? anyone know how i can get it to get past the error in rsd when flashing an sbf? im really hoping its a software error i can work around but its not looking to bright in my eyes. and it also didnt come with the factory sim card. i was wondering if maybe that could be causing the problem? thanks for any help guys.
help
jump454 said:
Just got this phone of ebay. Said it would power on but unable to get past boot up screen. They however didnt tell me there was also an error on screen. It says "Modem did not power up (3). Starting RSD protcol support." Battery too low to flash. So i went to my local radio shack to charge it on there universal charge. so i got the battery too low error to go away and my learning started from there. So i figured out what rsd was, got it and tries flashing an sbf to factory stock hoping the radio software got borked. But with no luck i keep getting the "error to switching phone to bp pass through mode". it will boot up no problem in "boot android (no bp)". so is the radio broke? anyone know how i can get it to get past the error in rsd when flashing an sbf? im really hoping its a software error i can work around but its not looking to bright in my eyes. and it also didnt come with the factory sim card. i was wondering if maybe that could be causing the problem? thanks for any help guys.
Click to expand...
Click to collapse
i have same problem too. who have any ideas? please help us
i dropped it (with the case still on it)and when i picked it up it reset by itself and when it did that it wouldn't leave the Motorola screen it just said couldn't start modem (3) and starting rsd protocol support. so every time it starts up it does that
Modem did not power up DRIVING ME NUTs
Thanks
I have the MetroPCS lgms769, I tried unlocking the bootloader but I guess I messed up some how. My screen had the touch screen problem, so I tried flashing again but now I'm stuck on security error. No matter what I do, I cannot get fastboot drivers to install for my phone. I've tried several times. It just sits there at waiting for omap44xx device. I've done the steps right to the T, My computer makes the sound as something connected then disconnected, then connected again and then once again disconnected. I've watched under device manager but I see nothing coming up, even when I do view all devices. I've booted into S/W upgrade mode but my phone is not detected. I can't boot to anything, it just goes to security error, shuts off, and boots showing my battery charging. I've installed all drivers through the LG website that goes with my phone. When my phone was working, I connected the usb and switched to every mode for it to install drivers. I'm on Windows 8 64 bit. Could someone please help me?
kseunder84 said:
I have the MetroPCS lgms769, I tried unlocking the bootloader but I guess I messed up some how. My screen had the touch screen problem, so I tried flashing again but now I'm stuck on security error. No matter what I do, I cannot get fastboot drivers to install for my phone. I've tried several times. It just sits there at waiting for omap44xx device. I've done the steps right to the T, My computer makes the sound as something connected then disconnected, then connected again and then once again disconnected. I've watched under device manager but I see nothing coming up, even when I do view all devices. I've booted into S/W upgrade mode but my phone is not detected. I can't boot to anything, it just goes to security error, shuts off, and boots showing my battery charging. I've installed all drivers through the LG website that goes with my phone. When my phone was working, I connected the usb and switched to every mode for it to install drivers. I'm on Windows 8 64 bit. Could someone please help me?
Click to expand...
Click to collapse
Funny you should mention this. I too have the same problem!! I spent all night to no avail! I managed to get clockwork to install, flash the backwards touch problem fix, but then when I attempted to install a Pacman 4.3 rom the phone rebooted to the Security Error Lg logo!! I can't flash any KDZ now because at 15% it loses a connection! I tried the Fastboot method and ADB just would not detect my phone! Pulling the battery out and having the phone connected to usb makes the device manager go nuts! Omap device pops in and out and wont stop! Thankfully I have the Tmobile premium handset protection package, so Ill get a replacement p769bk but OMG people don't try to unlock the boot loader on this device! Its not worth the risk and complexity/trouble!! Stick to root access and be happy! Wait and pray someone smart enough can figure out how to unlock the boot loader easily and with minimal risk! Before I messed with my phone I was on the OTA update v20F. I flashed to the V20B 760 KDZ and used the hex edited bin file that goes with it. Just don't do it! Its not worth the backwards menu/logo/touch headaches! Be warned!
I wound up taking it back to metropcs and I'm getting a new one in 3-5 days, they didn't charge me since the guy said it was a software problem and I was still within the 30 days
kseunder84 said:
I wound up taking it back to metropcs and I'm getting a new one in 3-5 days, they didn't charge me since the guy said it was a software problem and I was still within the 30 days
Click to expand...
Click to collapse
Good deal. Like I said before to anyone who reads this post:
Head my warning or you'll probably end up like the both of us!.
I really like this phone but damn! Why does LG have to lock the boot loader..? I miss having Cyanogen Mod. I mean my old P999 G2x wasn't this hard to get CWM/Root on it!
Somebody save the day! Find the key to a simple boot loader unlock! (V20F) This phone deserves it!
Hey you posted in the wrong place, anyways fastboot probably didn't work because you are on Windows 8.
If you try again, use this http://forum.xda-developers.com/showpost.php?p=45102887&postcount=1
This is the official program to restore from security error & other problems.
Sent from my LG-P769 using xda app-developers app
Thanks for trying to help but I tried to use that app and it still failed to detect my phone. I don't think I'll try it again. We need a new one click wonder app before I'll attempt this again. Also I don't think I like having a backwards LG logo stuck on my phone, ( I did not know that was going to stay there) yet alone some strange image mirror bug with the lock screen. It corrected itself if you hit the power button and wake it but if you reboot the phone it comes back.
Sent from my Nexus 7 using xda app-developers app
SovereignKnight said:
Thanks for trying to help but I tried to use that app and it still failed to detect my phone. I don't think I'll try it again. We need a new one click wonder app before I'll attempt this again. Also I don't think I like having a backwards LG logo stuck on my phone, ( I did not know that was going to stay there) yet alone some strange image mirror bug with the lock screen. It corrected itself if you hit the power button and wake it but if you reboot the phone it comes back.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
You can fix that with the proper u-boot.
Sent from my LG-P769 using XDA Premium 4 mobile app