[p769] rooted, think I softbricked my phone - LG Optimus L9 P760, P765, P768, P769

Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?

Flash kdz then install cwm then backup the stock ROM THEN do your mods. Every time every phone. Good luck
Sent from my LG-P769(20F) using the xda-developers app. If I helped you please hit the "thanks" button.

swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Yes, offline flash the kdz. Always backup your rom whenever you so something like that.
Sent from my LG-P769 using Tapatalk 4

If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769

kuma82 said:
If it's just the build.prop causing it not to boot, you can flash (with fastboot) the boot.img for the kdz you are on. Look at my signature on how to extract it.
If that doesn't work, flash the ice cream x & u partitions for p769 in fastboot, and then run offline flash
Fastboot info and help
http://forum.xda-developers.com/showthread.php?p=43703982
Install the locked bootloader cwm
http://forum.xda-developers.com/showthread.php?t=2095825
And use this busybox
https://play.google.com/store/apps/details?id=com.bitcubate.root.busybox.complete
Next time make a backup (make sure the backup is good, try to restore it)
CM 10.1 P769
Click to expand...
Click to collapse
Get outta here kuma, no one wants you here. -___- lol im jk.
Sent from my LG-P769 using Tapatalk 4

Lol, okay
NOT!
CM 10.1 P769

kuma82 said:
Lol, okay
NOT!
CM 10.1 P769
Click to expand...
Click to collapse
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?

swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
What variant do you have 769? Flash recovery.img in fastboot.
Sent from my LG-P769 using Tapatalk 4

swm5126 said:
Hi,
I'm not a newbie to Android by any measure, but this is my wife's phone, not mine (I have a Nexus 4) so I'm not familiar with a lot of the LG stuff.
Anyways, I rooted her phone to get rid of some of the bloatware and the stupid Qslide thing, and also to edit the build.prop so Netflix will have the Chromecast button. I had deleted quite a few bloatware system apps, and rebooted, everything was fine. I deleted a few more, then edited the build.prop. Rebooted.
Now it shows the LG logo, but then the screen goes blank, but is still on (you can see the backlight) and never boots. I only removed a few more of the LG and Tmobile apps and edited the model and manufacturer in the build.prop
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop

swm5126 said:
Thanks for the suggestions guys. I've tried the offline KDZ flashing it, but I can't get my computer (tried two actually, mine and my wife's laptop) to do anything once its in the S/W Upgrade mode. I used the method previously to update her phone the JB when Tmobile pulled the update. Since then it downloaded the most recent OTA. But anyways, I don't know why it wont work. It just continally tells me that my phone isn't connected, even though I'm using the latest drivers and the phone shows up correctly in the device manager. It's driving me nuts since it worked previously!
Any ideas?
Click to expand...
Click to collapse
Sorry I didn't break it down enough for you. You have to get fastboot up and running. Jellybean does not operate when starting in S/W mode, that's why you get the connection problem. Now ice cream, does operate when starting in the S/W upgrade mode. With fastboot you can flash everything you need to get the offline flash working. These three links are all the info you need.
Lelus fastboot
Select the option to flash x & u for p769
1. http://forum.xda-developers.com/showthread.php?p=41768774
Help if you can't get fastboot installed
2. http://forum.xda-developers.com/showpost.php?p=43210006&postcount=15
Info on how to use fastboot manually. Not really needed because lelus has everything needed in the first link.
3. http://forum.xda-developers.com/showthread.php?p=43642515
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Sorry I told you flashing the boot.IMG will help(was thinking of default.prop), I just remembered the build.prop is in the system partition.
CM 10.1 P769
---------- Post added at 11:00 PM ---------- Previous post was at 10:52 PM ----------
Lelus said:
boot into stock recovery "vol+"&"home"+"power"
adb should work and you can :
adb push busybox /tmp
adb push build.prop /tmp
adb shell
try "su" or "/system/bin/su" or "/system/xbin/su"
chmod 755 /tmp/busybox
/tmp/busybox mount -o remount,rw -t auto /system
/tmp/busybox cp /tmp/build.prop /system
/tmp/busybox chmod 644 /system/build.prop
Click to expand...
Click to collapse
Thanks for sharing, I didn't know stock recovery allowed ADB commands :thumbup:
CM 10.1 P769

swm5126 said:
Hi,
Do I have any easy options to fix this? Or do I need to flash the KDZ?
Click to expand...
Click to collapse
Factory LG mobile support tool has an option to "update recovery" in top right menu. This will download latest factory rom via internet and reflash phone in software update mode to reset everything.
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Works well.
might have to set phone into software update mode by pressing vol up and then inserting usb cable..

kuma82 said:
Please read each thread before starting and read the instructions txt found in Lelus fastboot zip
Click to expand...
Click to collapse
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?

swm5126 said:
Ok, I got the timing down and fastboot seems to come up, but after I can see the logo on my phone with the v 0.5, the script just says < waiting for device >. Thats where it should flash the ICS xloader? Or am I missing something and I should flash the JB images with fastboot? Where can I get the images?
Click to expand...
Click to collapse
Just kidding, got it figured out. Flashed the ICS xloader. Looks like its letting me restore finally! Thanks!

Related

[RECOVERY] [AT&T, TELUS, Bell, Rogers] Modified 3e recovery with adb root

Hi,
It's not CWM, but this is the stock 3e recovery + adb root access, allowing you to use adb to back up other partitions, restore, etc. etc.
Flash the pda-recovery-root.tar with Odin using the same instructions as for the Root kernel.
If someone who has not yet rooted could flash this and do the following from adb in recovery after:
Code:
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
adb pull /tmp/stock-kernel.img
adb shell rm /tmp/stock-kernel.img
then upload stock-kernel.img that would be good for making a return-to-stock odin image
Keep up with the awesome work brotha.
You're a maniac!!
<insert witty signature here>
I wake up to this! Nice! I cant wait for proper CWM.
Tomorrow will be a great day as I'm holding mine
Sent from my MB860 using xda premium
telus galaxy note
hi, i tried to back up the kernel for the canadian telus galaxy note with the adb root you have there but when i use adb to run the commands i get an error message saying permission denied. does it work with the canadian version?
Hi, I haven't tested with anything other than the AT&T GNote. Do you get the # root prompt in adb? You likely wouldn't even have adb without the mod working, what error do you get for what command exactly?
when i run
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
i get
/dev/block/mmcblk0p8: cannot open for read: Permission denied
then again do i have to be in recovery mode fir before i run adb? just figured out how to get into recovery.
Since I'm in Canada with the Rogers variant I was going to upload the stock kernel, but somehow I just cannot get into recovery to pull it, I've tried vol up+power, both volumes+power, and obviously vol down+ power is download mode. It's almost embarrassing haha.
I've always made good use of what the dev's have done for us since my N1, I figured I could give back at least a little
looks like i had to be in recovery mode. how big is the kernel suppose to be mine shows about 10MB
---------- Post added at 10:55 PM ---------- Previous post was at 10:53 PM ----------
to get into recovery mode hold vol + and vol - and turn on the phone holding the volume keys and release the power key
Da_G...
I have been a big fan of yours for a long time... You had the BEST Windows 6.5 ROMS I ever used and have always done a lot for the community...
I cannot tell you how happy I was to see that you have this phone and are working on it!
Just wanted to sing your praises
Can't wait to see your new stuff!
Da_G said:
Hi,
It's not CWM, but this is the stock 3e recovery + adb root access, allowing you to use adb to back up other partitions, restore, etc. etc.
Flash the pda-recovery-root.tar with Odin using the same instructions as for the Root kernel.
If someone who has not yet rooted could flash this and do the following from adb in recovery after:
Code:
adb shell dd if=/dev/block/mmcblk0p8 of=/tmp/stock-kernel.img
adb pull /tmp/stock-kernel.img
adb shell rm /tmp/stock-kernel.img
then upload stock-kernel.img that would be good for making a return-to-stock odin image
Click to expand...
Click to collapse
Thank you for the fantastic work.. Do you have a github or other place we can fetch sources?
Guess this is my cue to get in for the Bell variant.
I'm guessing flashing this will also hit the counter too? Right...
Sent from my Galaxy Nexus using Tapatalk
Ignore me. I goofed up.
@FarBeyond: Thanks!
@runandhide05: yep.
Much appreciated, pattmyn
(unfortunately it looks like you pulled p8 which is the kernel, but had already flashed the root kernel, overwriting the bell stock kernel.)
(however, you can get the bell rom by following the same directions but substituting p24 instead of p8. note that it will be much larger!)
Da_G said:
@FarBeyond: Thanks!
@runandhide05: yep.
Much appreciated, pattmyn
(unfortunately it looks like you pulled p8 which is the kernel, but had already flashed the root kernel, overwriting the bell stock kernel.)
(however, you can get the bell rom by following the same directions but substituting p24 instead of p8. note that it will be much larger!)
Click to expand...
Click to collapse
F***. I've already got your kernel back installed again, and started debloating the Bell one. Tell ya what, if nobody hops on it by tomorrow evening, I'll nuke and reboot back in and pull the larger ROM file. I've just run out of time tonight and have to get back to working on work related stuff.
Edit: As a funny aside, my counter's gonna be in the double digits at this rate. I REALLY hope I don't have to send this thing back lol
I'm already in the 20s myself Can't concern yourself about such things as a dev!
Sent from my SAMSUNG-SGH-I717 using Tapatalk
http://www.mediafire.com/?6atiy1dddr42hp3
telus kernel
G, if i pull the whole rom from the device does that include all the stuff i have put on it already? or just the factory image?
Thanks for the stock TELUS kernel
I've incorporated some of the ramdisk components into my ramdisk for the next version (I used ramdisk from Skyrocket there) - differences are minor.
I'll get an odin-to-stock-TELUS-kernel image up tomorrow!

Out of ideas!

Hey guys, I'm in need of some help with my prime. Just got it a few days ago and rooted it just fine using vipermod. The used OTA root keeper to save root for ICS. After installing ICS, I restored root and everything was fine. Then I noticed that my prime would loose wifi signal ever 2 minutes. I did a factory reset thinking that would fix it (and it did) but now a few things are beyond messed up and i can't figure it out! For one, I cannot access the notifications area (when i tap it, nothing comes up) the home button also does not work at all. so i tried to install cwm so i can re flash the ROM from scratch but now ADB does not see my device AT ALL. i tried everything. i have all the drivers installed and all. I'm at a loss and extremely frustrated. does anyone know whats going on here? how can i get adb to see my prime so i can flash cwm? or is there an alternative way to completely flash the rom? (i also tried the method on asus' website by downloading ICS and placing it on the root of the SD, and still nothing)
You won't be able to install CWM without unlocking the bootloader (and voiding your warranty first). After that, you can no longer flash a ROM from Asus without bricking your device. There is the latest updated ROM in the dev section though.
Good luck!
I did that as well and still nothing :-/
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
scook9 said:
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
Click to expand...
Click to collapse
yup thats enabled as well. when i first got it with 3.2 on it, i plugged it in and drivers installed automatically and adb recognized it right away. now that ics is on it, adb cant see it. i have never ran into this with any android device ever.
Mine did that once and I also had to disable ASUS Sync in settings. After that ADB worked fine.
Update the drivers on your PC
http://forum.xda-developers.com/showthread.php?t=1426502
If you do it right, it will work.
BUT YOU DONT EVEN NEED ADB, LOOK BELOW (I am not advocating not knowing how to adb but lets just fix your prime)
Since you have unlocked your bootloader you can install CWM and just install the latest Virtuous Rom:
If you dont have CWM download Rom Manager from the market, run it, select "Flash recovery" at the top. (btw rom manager just released this today)
*Note that the 'reboot into recovery' option within RM will not reboot into recovery, you must do it manually.. See below
-Backup your apps with Titanium Backup if you want
-Download Virtuous S
-Boot into recovery (directions beneath)
---Power off
---Hold Vol Down (-) and Power until you see spash screen with white text at the top THEN HIT VOL UP (+) within 5 seconds. this will boot into recovery
-if you are coming from stock then: select "wipe data/factory reset"
-Install zip from sdcard, browse for the rom
-Profit?
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Nissan350 said:
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Click to expand...
Click to collapse
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
mtotho said:
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
Click to expand...
Click to collapse
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Nissan350 said:
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Click to expand...
Click to collapse
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
mtotho said:
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
Click to expand...
Click to collapse
Awsome, thanks again man

[SOLVED] help! phone won't boot into system or recovery!

SOLVED, see post #6
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
=JKT= said:
I have been trying out the various roms for Atrix
I tried the same zip of Neutrino EE 2.9 that I used to flash that rom before (since it worked great!) This time I also flashed the gtalk and sync addons. I did the usual wiping of everything.
Now the phone bootloops at the moto logo, and when I try to boot back into TWRP, I get stuck at the TWRP splash screen.
My computer isn't recognizing the device on fastboot either. DANG!
can someone help me out?
Click to expand...
Click to collapse
okay, I just found out that I can access adb in the state that recovery is in.
Is it possible to reflash either the rom or the recovery from a shell in here? or would that be "bootstrapping" since I'm already in recovery?
perhaps I can adb push a backup to /system?
of course the ./adb reboot bootloader doesn't work
I'm using a mac and I've had trouble getting fastboot to recognize my device in the past...I think last time I just borrowed someone's pc to do it.
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Can't test it right now, but I think the process would go something like this (recovery means on the phone, computer means on the computer):
Code:
[I]recovery>[/I] mount /sdcard
[I]computer>[/I] adb push recovery.img /sdcard/
[I]recovery>[/I] flash_image recovery /sdcard/recovery.img
[I]recovery>[/I] umount /sdcard
[I]recovery>[/I] reboot recovery
Note once again that this is untested, it's straight from my head, so it might need adjustments.
ravilov said:
You could use what's left of the recovery to flash a fresh recovery. The same one or a different one, doesn't matter. That might make the recovery work properly.
Click to expand...
Click to collapse
thanks for the idea. I can't access any of the functions of the recovery. it's just a splash screen. ADB recognizes the device on my computer though. I can adb push files...I'm wondering if I can push something from a backup to my phone through adb. I guess I'd need to push the /system and /boot to it. I can't seem to get mmcblk0p12 to mount though...
edit: I didn't see the code you added.
I tried it and got this message:
error scanning partitionsfailed with error: -1
I can't seem to get any partitions to mount (ie mmcblk0p12 etc)
I'm nervous about totally borking recovery since it's my only access to the phone right now. I might have to borrow a pc to get fastboot to work.
=JKT= said:
I might have to borrow a pc to get fastboot to work.
Click to expand...
Click to collapse
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
[SOLVED]
ravilov said:
Might be a good idea. Macs are clearly doomed on this.
(Yet another reason I dislike them. )
Internal partitions might be borked, that could be why you can't mount them. That's why I suggested you flash recovery via /sdcard (external sdcard). However, I agree trying to overwrite recovery in this unstable state is kinda risky. Functional fastboot would be much better.
Click to expand...
Click to collapse
SOLVED!!
First I found out that if I type fastboot -i 0x22b8 before every command, they worked fine.
then I stumbled across moto-fastboot, which is apparently a special fastboot for moto devices.
I used that to flash a new recovery the standard way and it worked out just fine.
Thanks so much for your help, ravilov!!
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
ravilov said:
No problem, glad you have it up and running again.
And yeah... I thought you knew about moto-fastboot already, it's a pretty well known thing around here? :dunno:
Either way, now at least you have a working fastboot on your own computer.
Might want to change the thread title to "SOLVED".
Click to expand...
Click to collapse
I've only had the Atrix for about a week. Still learning the ropes: coming from an HTC device, so I'm used to doing things a certain way and relearning some basics lol
Cheers!
Sent from my MB860 using xda app-developers app

Mirrored Screen and Touchscreen issues

I have been looking EVERYWHERE for a solution to this. I followed the {Unlock Bootloader for Noobs} to the letter http://forum.xda-developers.com/showthread.php?t=2277639
I get to where in the video guide the screen become's inverted and the touchscreen is all over the place. But I can't get my phone to boot into recovery. I have tried every single guide to no avail. I have the LG L9 P769 with Tmobile.
And right now my phone is useless.
Just a tid bit, when it first boot's up both the logo and everything is backwards, but if I suspend it and bring it back up, its all back to normal but the touch pad is still goofed up.
Any help would be greatly appreciated.
You need Roberts busybox installed, artas182x cwm install, and flash the fix with cwm.
You need the v6 bin the directions are with it.
Sent from my LG-P769 using xda app-developers app
I rerooted the phone, installed SU, gave root access to the recovery when it asked, installed and clicked "Boot into Safemode" and it did the exact same thing it always does.... nothing, it simply rebooted the phone to main screen, Even tried holding down the vol- button during a boot.. nothing. it only goes into safemode.
Feral_Sparky said:
I rerooted the phone, installed SU, gave root access to the recovery when it asked, installed and clicked "Boot into Safemode" and it did the exact same thing it always does.... nothing, it simply rebooted the phone to main screen, Even tried holding down the vol- button during a boot.. nothing. it only goes into safemode.
Click to expand...
Click to collapse
Do you know how to use ADB with your computer? Do you have android debugging enabled? Do it the old way
First extract the v6.bin to you SD card (external_SD). Open adb and enter the following
Code:
adb shell
su (give it root access on your phone, good luck)
cat /storage/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
once you do that the shell will freeze (can't use it anymore) So open a new cmd and enter this
adb reboot
This will fix the problem. Now go thank Lelus :thumbup:
CM 10.1 P769
Where do I find the v6.bin to copy to my phone?
Feral_Sparky said:
Where do I find the v6.bin to copy to my phone?
Click to expand...
Click to collapse
Meda808 posted it above.
CM 10.1 P769
I did just as you told me to, I copied the v6.bin to my external sd card, started up ADB, put in the commands but once I entered SU and gave it root on the phone the terminal stopped and would not allow any more commands, I rebooted and tried again as well as rebooting the phone. I am unable to enter the command to transfer the file.
Feral_Sparky said:
I did just as you told me to, I copied the v6.bin to my external sd card, started up ADB, put in the commands but once I entered SU and gave it root on the phone the terminal stopped and would not allow any more commands, I rebooted and tried again as well as rebooting the phone. I am unable to enter the command to transfer the file.
Click to expand...
Click to collapse
You might have thought you gave it access, but actually denied access. Try to open supersu, and check if adb was given su access.
CM 10.1 P769
kuma82 said:
You might have thought you gave it access, but actually denied access. Try to open supersu, and check if adb was given su access.
CM 10.1 P769
Click to expand...
Click to collapse
I checked supersu and it show's as given root access. And when I put in the SU command into adb it show's on the phone as giving root permission's via popup. And that's where it freezes.
Do you have team viewer setup, send me your info in a PM. I'll wait for 30 mins
CM 10.1 P769
kuma82 said:
Do you have team viewer setup, send me your info in a PM. I'll wait for 30 mins
CM 10.1 P769
Click to expand...
Click to collapse
Sorry it took so long to reply, I am setting it up now. Gotta love having kids
Go figure we couldnt get it to work, only been trying since I got the thing back in March to no success. But I do appreciate the help.... now im off to brick my phone to get a new one.
I removed because someone won't listen and just do what I posted Lol. I'm pm you
---------- Post added at 08:51 PM ---------- Previous post was at 08:23 PM ----------
Feral_Sparky said:
Go figure we couldnt get it to work, only been trying since I got the thing back in March to no success. But I do appreciate the help.... now im off to brick my phone to get a new one.
Click to expand...
Click to collapse
Lol, while you are at it, might as well remove the u-boot
CM 10.1 P769
kuma82 said:
Do you know how to use ADB with your computer? Do you have android debugging enabled? Do it the old way
First extract the v6.bin to you SD card (external_SD). Open adb and enter the following
Code:
adb shell
su (give it root access on your phone, good luck)
cat /storage/external_SD/v6.bin > /sys/devices/virtual/input/lge_touch/firmware
once you do that the shell will freeze (can't use it anymore) So open a new cmd and enter this
adb reboot
This will fix the problem. Now go thank Lelus :thumbup:
CM 10.1 P769
Click to expand...
Click to collapse
Thanks! This fixed the touch screen on P769 Tmobile. This is after using the LG support tool to update back to V20f from a failed attempt using carloswii5's noob guide. Could not get past "adb reboot oem-unlock."
If anyone can point me in the right direction to get the LG boot screen back to normal (not inverted/mirrored) i would appreciate it. -----Update:found u-boot.zip fix for boot screen.
Thank You!
Thank You!
I had given up on this a year ago, I tried it again on my phone and it worked!
Thanks Again

Can't boot into Recovery, Bootloader, Download, or Fastboot! Why?

I have an LG Optimus Fuel (LG L34C) from Straightalk running Android 4.4. This phone is (as far as I know) the same as the LG Optimus Zone 2 from Verizon Prepaid.
I couldn't find a halfway decent manual for the LG L34C so I followed the LG Optimus Zone 2 Manual to enter Recovery mode. When I held the buttons on the L34C, it would boot, show the LG logo, then shut off, show the LG logo, and do it again. As long as the buttons were held in would loop.
So I downloaded the ADB and tried to do it from there.
"adb reboot recovery" brings up the classic "No Command".
"adb reboot bootloader" just reboots it.
"adb reboot download" just reboots it.
"adb reboot fastboot" just reboots it.
What the heck is going on! I'm going crazy trying to figure this out. Why can't I access any of the special menus?
Oh, and TowelRoot didn't work to root the phone either.
I tried to enter Recovery Mode on my Nexus 7 (2012) and noticed that I also get the "No Command" prompt. I was then able to hold 'Power' and press 'Volume Up' to enter Recovery mode.
I tried this, and every other imaginable button combination, on the LG Optimus Fuel and had no luck whatsoever.
Is it possible that this stuff has been disabled by LG?
vwnut13 said:
I tried to enter Recovery Mode on my Nexus 7 (2012) and noticed that I also get the "No Command" prompt. I was then able to hold 'Power' and press 'Volume Up' to enter Recovery mode.
I tried this, and every other imaginable button combination, on the LG Optimus Fuel and had no luck whatsoever.
Is it possible that this stuff has been disabled by LG?
Click to expand...
Click to collapse
I to have same prob with it seems factory reset is done thru safemode We need the firmware to get somewhere
toxinburn said:
I to have same prob with it seems factory reset is done thru safemode We need the firmware to get somewhere
Click to expand...
Click to collapse
Is your device activated. Straight Talk said that reset via recovery (it's in the phones manual...) would work after activated, but that seems like BS.
full user guide from LG
Okay I got the full user guide that was NOT included this is the LG Full guide. Just Click it, had to put it on 4shared as it is too large to upload as .pdf on here.
Root worked for me after I followed this guide. http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/ Make sure you change the values in post #1, and remounting /system as explained in reply #1.
vwnut13 said:
I have an LG Optimus Fuel (LG L34C) from Straightalk running Android 4.4. This phone is (as far as I know) the same as the LG Optimus Zone 2 from Verizon Prepaid.
I couldn't find a halfway decent manual for the LG L34C so I followed the LG Optimus Zone 2 Manual to enter Recovery mode. When I held the buttons on the L34C, it would boot, show the LG logo, then shut off, show the LG logo, and do it again. As long as the buttons were held in would loop.
So I downloaded the ADB and tried to do it from there.
"adb reboot recovery" brings up the classic "No Command".
"adb reboot bootloader" just reboots it.
"adb reboot download" just reboots it.
"adb reboot fastboot" just reboots it.
What the heck is going on! I'm going crazy trying to figure this out. Why can't I access any of the special menus?
Oh, and TowelRoot didn't work to root the phone either.
Click to expand...
Click to collapse
i don't know what the heck i did but i got into the recovery. problem is i bricked my device and i need firmware lol. anyone been able to get the OTA firmware zip? if so i need it like,really bad. what i did was i just held down pwr and vol- for like 4 reboots and let go of the power button and then it vibrated twice and i was suddenly somehow in?
---------- Post added at 07:51 AM ---------- Previous post was at 07:46 AM ----------
yackaro said:
i don't know what the heck i did but i got into the recovery. problem is i bricked my device and i need firmware lol. anyone been able to get the OTA firmware zip? if so i need it like,really bad. what i did was i just held down pwr and vol- for like 4 reboots and let go of the power button and then it vibrated twice and i was suddenly somehow in?
Click to expand...
Click to collapse
now that i think about it my device was bricked.... maybe this is a special recovery designed to act only when problems are detected in the boot sequence?
Well, looks like I'm in the same boat now, lol. Going against everything I've learned in the 5 years messing with Android, I had a non-thinking DOH! moment and changed the screen density. After reboot, I just have a bootlooping cheap paperweight for the time being. I can get into recovery, but there's no menu options. I am going to try to push the backed-up build.prop.
They really have this one locked down. I haven't found an OTA zip in my searches yackaro, but I'll keep an eye out for you.
root for lg fule kinda works
I got an lg fule from walmart and decided to root it(never done it befor on any thing)I tried for at least 6 hrs and tied poot z4 all kinds of apks and finely I get towelroot to work but I cant get full acces its says setuid attribute is NOT present BUT root user ownership is present. root access is NOT correctly configured for this file! what is wrong and what do I need to do? I have been using the phone for a week downloading apps from blackmarket and googls app sometimes its kinda slow but It wont let me move systems apps to sd,can delet but not movei have titanium bu supersu busybox pro force2sd esfx and rommaneger how or can I gain full root for kitkat 4.4 lg fuel?
It is possible that TracFone (StraightTalk is a subsidiary of TracFone) is using special bootloader code to lock users out of recovery mode. I know that T-Mobile did something like that with some lower-to-mid-range LG phones.
ColtonDRG said:
It is possible that TracFone (StraightTalk is a subsidiary of TracFone) is using special bootloader code to lock users out of recovery mode. I know that T-Mobile did something like that with some lower-to-mid-range LG phones.
Click to expand...
Click to collapse
I can't (well, couldn't - I'm soft bricked right now) even boot into bootloader. To get full root, I think we need an unlocked boot loader. However, "ADB reboot bootloader" doesn't work, right now, as well as most of all the other commands.
I was able to reboot into recovery, but there wasn't any text. I'm working on getting the fuel booting again, but I haven't found anything that works yet. The hard key combo that LG describes to hard reset doesn't work. And I've tried many other hard key combinations, but nothing works so far. [emoji20]
skyline247 said:
I can't (well, couldn't - I'm soft bricked right now) even boot into bootloader. To get full root, I think we need an unlocked boot loader. However, "ADB reboot bootloader" doesn't work, right now, as well as most of all the other commands.
I was able to reboot into recovery, but there wasn't any text. I'm working on getting the fuel booting again, but I haven't found anything that works yet. The hard key combo that LG describes to hard reset doesn't work. And I've tried many other hard key combinations, but nothing works so far. [emoji20]
Click to expand...
Click to collapse
Yes, what I meant is they might be blocking both recovery, and boot loader mode...
Sent from my HTC One (M8)
ColtonDRG said:
Yes, what I meant is they might be blocking both recovery, and boot loader mode...
Sent from my HTC One (M8)
Click to expand...
Click to collapse
True. They probably are. I don't know why they would block at least hard factory reset, though. But then again, since we paid for our device (albeit only $30) seems like we could have more freedom with it. Oh well.
LG has fastboot locked out. I was browsing the LG G2 forums when I found that people are able to get to fastboot by zeroing out their 'laf' partition and forcing the phone into fastboot (because aboot can't find it) where we can then flash a custom recovery.img hopefully. I have the recovery partition extracted and replaced /sbin/recovery with CWM and repacked. I just need to get into fastboot to test it. I will get a second phone from walmart to dev with, they're only $30. if anyone has a dev phone to test it on, read on...
This is theory and hasen't been tested. We may not even be able to run custom recovery or fastboot.
If anyone wants to pick up here be sure you have fastboot and adb installed and have some dev knowledge, not for noobs like me.
backup your laf partition to an external SD card (insert a micro SD)
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/laf.img
pull laf.img to your computer as a backup and to use later in fastboot
wipe your laf partition [I AM NOT RESPONSIBLE IF YOU KILL YOUR PHONE]
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
reboot your phone and connect it to your computer.
your phone SHOULD (I have not tested this) boot into fastboot as a failsafe.
on your computer
Code:
fastboot flash laf laf.img
Code:
fastboot reboot
phone should reboot back to normal.
This will test that we can in fact get to fastboot.
STOCK laf, boot & recovery files to look at. The included repacker does not repack the images properly. I use linux tools for repacking.
https://dl.dropboxusercontent.com/u/14669363/LGL36C.rar
FlyingPoo said:
LG has fastboot locked out. I was browsing the LG G2 forums when I found that people are able to get to fastboot by zeroing out their 'laf' partition and forcing the phone into fastboot (because aboot can't find it) where we can then flash a custom recovery.img hopefully. I have the recovery partition extracted and replaced /sbin/recovery with CWM and repacked. I just need to get into fastboot to test it. I will get a second phone from walmart to dev with, they're only $30. if anyone has a dev phone to test it on, read on...
This is theory and hasen't been tested. We may not even be able to run custom recovery or fastboot.
If anyone wants to pick up here be sure you have fastboot and adb installed and have some dev knowledge, not for noobs like me.
backup your laf partition to an external SD card (insert a micro SD)
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/laf of=/storage/external_SD/laf.img
pull laf.img to your computer as a backup and to use later in fastboot
wipe your laf partition [I AM NOT RESPONSIBLE IF YOU KILL YOUR PHONE]
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
reboot your phone and connect it to your computer.
your phone SHOULD (I have not tested this) boot into fastboot as a failsafe.
on your computer
Code:
fastboot flash laf laf.img
Code:
fastboot reboot
phone should reboot back to normal.
This will test that we can in fact get to fastboot.
STOCK laf, boot & recovery files to look at. The included repacker does not repack the images properly. I use linux tools for repacking.
https://dl.dropboxusercontent.com/u/14669363/LGL36C.rar
Click to expand...
Click to collapse
Sounds like we are a little closer, however you can push a .img thru adb already I know some people that did a mako build only problem is it bricked it.
thatguyrightthere said:
I got an lg fule from walmart and decided to root it(never done it befor on any thing)I tried for at least 6 hrs and tied poot z4 all kinds of apks and finely I get towelroot to work but I cant get full acces its says setuid attribute is NOT present BUT root user ownership is present. root access is NOT correctly configured for this file! what is wrong and what do I need to do? I have been using the phone for a week downloading apps from blackmarket and googls app sometimes its kinda slow but It wont let me move systems apps to sd,can delet but not movei have titanium bu supersu busybox pro force2sd esfx and rommaneger how or can I gain full root for kitkat 4.4 lg fuel?
Click to expand...
Click to collapse
It's the new security features of kitkat. Only allows apps to access their own folders. Try SDFix (root app from play store ). I now can read, write, copy to/ from sd or system.
Sent from my LGL34C using XDA Free mobile app
---------- Post added at 09:16 PM ---------- Previous post was at 08:55 PM ----------
@FlyingPoo
Some things that I noticed that were missing (besides /sbin/recovery). There is no flash_image, dump_ image, or erase_ image in /system/ bin. Usually use flash_ image in terminal or in fastboot. Don't know if these binaries are generic, or device specific (partitions). Could copy from other device, but don't know if they will work properly. Glad I'm not alone in this.
Sent from my LGL34C using XDA Free mobile app
---------- Post added at 10:00 PM ---------- Previous post was at 09:16 PM ----------
[/COLOR
@FlyingPoo
What cwm are you going to use? Optimus Zone? Or did you compile it for the fuel?
Sent from my LGL34C using XDA Free mobile app
ibub said:
What cwm are you going to use? Optimus Zone? Or did you compile it for the fuel?
Click to expand...
Click to collapse
I pulled the one in the Zone since that phone is most similar to ours, However I have a feeling the key bindings won't be correct, so I may still have to compile from source. I pulled the git for TWRP but haven't made changes to it yet. Its been a busy week at work and its only monday.
---------- Post added at 08:49 PM ---------- Previous post was at 08:27 PM ----------
ibub said:
Some things that I noticed that were missing (besides /sbin/recovery). There is no flash_image, dump_ image, or erase_ image in /system/ bin. Usually use flash_ image in terminal or in fastboot. Don't know if these binaries are generic, or device specific (partitions). Could copy from other device, but don't know if they will work properly. Glad I'm not alone in this.
Click to expand...
Click to collapse
Those also don't exist in the stock recovery for the Optimus Zone. It looks as if busy box was added to the Zone CWM recovery now that I have looked at it closer. Its been a WHILE (Samsung Vibrant with Team Whiskey) since I built a recovery image.
FlyingPoo said:
I pulled the one in the Zone since that phone is most similar to ours, However I have a feeling the key bindings won't be correct, so I may still have to compile from source. I pulled the git for TWRP but haven't made changes to it yet. Its been a busy week at work and its only monday.
---------- Post added at 08:49 PM ---------- Previous post was at 08:27 PM ----------
Those also don't exist in the stock recovery for the Optimus Zone. It looks as if busy box was added to the Zone CWM recovery now that I have looked at it closer. Its been a WHILE (Samsung Vibrant with Team Whiskey) since I built a recovery image.
Click to expand...
Click to collapse
Yeah, we might only get one shot at success (before jtag ), so it's probably best to compile from our recovery and source. I used Apktool to decompile recovery (dd if =dev/ block/ mmcblk0p17 of =/cache/ testrecovery/recovery.img). Ramdisk has./ sbin/recovery. Copied that to /Sbin/ . Disappears after reboot. Haven't yet decompiled boot.img. Hoping to find "boot", and fastboot. More later.
Sent from my LGL34C using XDA Free mobile app
@FlyingPoo
Do you know anything about the Loki tool by Dan Rosenberg:
https://github.com/djrbliss/loki/blob/master/README.txt
Have to admit that I'm not quite this educated, but that looks promising.
Edit: This is like having to root your phone twice. Lol
EDIT: Don't nuke laf yet! I dd and decompiled it (had to rename it to boot.img in Apktool). There are some interesting images (png) in res folder. I'm gonna dd aboot and abootb, and see what's there. Gotta go to work soon. Probably more tomorrow.
Sent from my LGL34C using XDA Free mobile app
ibub said:
@FlyingPoo
Do you know anything about the Loki tool by Dan Rosenberg:
https://github.com/djrbliss/loki/blob/master/README.txt
Have to admit that I'm not quite this educated, but that looks promising.
Edit: This is like having to root your phone twice. Lol
EDIT: Don't nuke laf yet! I dd and decompiled it (had to rename it to boot.img in Apktool). There are some interesting images (png) in res folder. I'm gonna dd aboot and abootb, and see what's there. Gotta go to work soon. Probably more tomorrow.
Sent from my LGL34C using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for all your work. Im also very interested in being able to boot into stock recovery. Mainly to be able to preform a factory reset. Do you know of an alternative method to do a factory reset at this time since booting into any recovery isnt possible ATM?

Categories

Resources