Related
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!
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
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?
Hi, I found out that there are official cyan roms now and I wanted to test them. For root, I installed kingroot app. Then I used the app flashify for flashing newest TWRP (from this forum) on my device, and it also says it is done, but after reboot, i get a pink screen with some kind of ram dump text. I can restart into normal android from g2 mini, but I want to use marshmallow.
Euathlus1985 said:
Hi, I found out that there are official cyan roms now and I wanted to test them. For root, I installed kingroot app. Then I used the app flashify for flashing newest TWRP (from this forum) on my device, and it also says it is done, but after reboot, i get a pink screen with some kind of ram dump text. I can restart into normal android from g2 mini, but I want to use marshmallow.
Click to expand...
Click to collapse
Can u post the image plzz? Someone might help u. ( I can too)???
tra_dax
Well I uploaded a picture to gdrive, but I cant post this link here Ok, it works with CODE tag.
Code:
https://drive.google.com/00b54106-bfd9-49ed-9f1e-550ea1df1ec9
It seems like I need to unlock the bootloader too, I downloaded this file and Terminal Emulator and typed in everything, but it says "permission denied"
Euathlus1985 said:
Well I uploaded a picture to gdrive, but I cant post this link here Ok, it works with CODE tag.
Code:
https://drive.google.com/00b54106-bfd9-49ed-9f1e-550ea1df1ec9
It seems like I need to unlock the bootloader too, I downloaded this file and Terminal Emulator and typed in everything, but it says "permission denied"
Click to expand...
Click to collapse
Well u need to install busy box first, and install the terminal emulator.
Download the 2.8.7.0 twrp IMG from here
http://forum.xda-developers.com/attachment.php?attachmentid=3385522&d=1435697303
Place the file in the root of the SD card and open the terminal emulator and run this command.
su
dd if=/sdcard/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Wait till whole process is over and then type
su
reboot recovery
That's all.
tra_dax
Hi, my G2 Mini's name is D620r, can I use this image anyway?
And what the heck is this busy box?
Euathlus1985 said:
Hi, my G2 Mini's name is D620r, can I use this image anyway?
And what the heck is this busy box?
Click to expand...
Click to collapse
U need to install busy box in order to run Linux commands. The IMG file will work on g2 mini's all variants. But if u want u can search and satisfy urself.
tra_dax
And wher do I have to type this whole stuff you wrote in busybox or this terminalemulator?
Euathlus1985 said:
And wher do I have to type this whole stuff you wrote in busybox or this terminalemulator?
Click to expand...
Click to collapse
In the terminal emulator.
tra_dax
Still not working, I installed the app busybox and also what the app wanted to install, I typed everything in terminal emulator like this
Code:
https://drive.google.com/file/d/0Bxuuoq6jYFMsUWxxUHRVZTItZkk/view?usp=sharing
After this I only typed reboot recovery, the smartphone restarts and ends in this pink screen, but before that is a black screen with a text "Error: Secure boot" or something like this.
Euathlus1985 said:
Still not working, I installed the app busybox and also what the app wanted to install, I typed everything in terminal emulator like this
Code:
https://drive.google.com/open?id=0Bxuuoq6jYFMsUWxxUHRVZTItZkk
After this I only typed reboot recovery, the smartphone restarts and ends in this pink screen, but before that is a black screen with a text "Error: Secure boot" or something like this.
Click to expand...
Click to collapse
I think so that's the bootloader, did u unlock it?
tra_dax
I thought this was to unlock the bootloader!?
EDIT: Here the picture
Code:
https://drive.google.com/file/d/0Bxuuoq6jYFMsUWxxUHRVZTItZkk/view?usp=sharing
Euathlus1985 said:
I thought this was to unlock the bootloader!?
EDIT: Here the picture
Code:
https://drive.google.com/file/d/0Bxuuoq6jYFMsUWxxUHRVZTItZkk/view?usp=sharing
Click to expand...
Click to collapse
Ok, to unlock the bootloader download the aboot.img from here:
http://forum.xda-developers.com/g2-mini/development/bootloader-unlock-t2827748
And rename it as aboot4.img
And then open the terminal emulator and type this code:
su
dd if=/sdcard/aboot4.img of=/dev/block/platform/msm_sdcc.1/by-name/aboot
There's a video on YouTube about the whole process, I would suggest u to watch it before u perform it.
After bootloader is unlocked, use the first code that I gave u to flash the recovery accordingly.
If u find any difficult then quote me.
Best of luck??
tra_dax
Euathlus1985 said:
Hi, I found out that there are official cyan roms now and I wanted to test them. For root, I installed kingroot app. Then I used the app flashify for flashing newest TWRP (from this forum) on my device, and it also says it is done, but after reboot, i get a pink screen with some kind of ram dump text. I can restart into normal android from g2 mini, but I want to use marshmallow.
Click to expand...
Click to collapse
the same thing happened with me and in my case I had to take the technical assistance ... then I found out you have to go back to KITKAT STOCK rom because it accepts bootloader unlock by this method !! excuse my bad english
Hi there guys,
I'm new to the forum so apologies if this has been posted in the wrong place.
So I was directed to this forum to attempt to solve a different problem but in my hast, I have caused an even bigger problem!
So initially I was having problems with the new Android Wear update with regards to rooting, so I wanted to find a way to roll the software back or restore the device to stock.
I came across this post http://forum.xda-developers.com/g-watch/development/tool-lg-g-watch-return-to-stock-t3158349 and attempt to do as advised, but half way through the process, the program froze. I then tried to reset the watch from the button at the back, but the watch is now stuck on the fastboot menu. I used ADB to see if I could still connect to the device but no devices can be found.
I have checked the device manager and can see the device as "Android Bootloader Interface" but can't seem to get it past the fastboot menu.
Any help would be much appreciated.
Thanks in advance.
just do it again, as long you can get fastboot, you are safe.
Jaocagomez said:
just do it again, as long you can get fastboot, you are safe.
Click to expand...
Click to collapse
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Montezz1 said:
The problem is, the program requires a connection via ADB, but ADB can no longer see the device. So when I try to run it again, nothing happens :/
Click to expand...
Click to collapse
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Xmaster24 said:
F the program it is outdated as **** get adb minimal here and the last 5.1.1 images here
Extract to the same folder you put adb minimal and open a terminal here.
do these commands:
Code:
fastboot flash boot nameofboot.img
fastboot flash system nameofsystem.img
(optional) fastboot flash recovery recovery.img
fastboot format/erase data
fastboot format/erase cache
Oh yeah btw if the only problem you had was with rooting just use my guide here and system images from here instead
Click to expand...
Click to collapse
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Montezz1 said:
Hi there,
Thanks for the response.
I have just completed the steps as advised, download the minimal ADB and fastboot and extracted the G Watch images into that file. I opened ADB and ran the following command:
Code:
fastboot flash boot nameofboot.img
But received the following error:
http://i.imgur.com/URh0IsF.png
Any ideas on how to solve that error?
Thanks in advance
Click to expand...
Click to collapse
Check the bootloader lock status and report back
Xmaster24 said:
Check the bootloader lock status and report back
Click to expand...
Click to collapse
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Montezz1 said:
Secure boot - Enabled
Lock state - unlocked.
I did try to unlock it again just to make sure and it is showing that is it unlocked.
Click to expand...
Click to collapse
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Xmaster24 said:
Do this command:
flashing get_unlock_ability
and also try and flash another partition eg system and report back what happens
Click to expand...
Click to collapse
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Montezz1 said:
Hi,
The result from the flashing get_unlock_ability command is provided here:
http://i.imgur.com/jczJRST.png
I attempted to flash the system image and received the following error:
http://i.imgur.com/83RXdFi.png
The watch responses the same as when attempting to flash the boot image and is stuck on "Downloading".
I also tried to flash the recovery image and received the same error as shown when flashing the boot image.
Thanks
Click to expand...
Click to collapse
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Xmaster24 said:
Looks like it is either that adb minimal is messed up (I use the full 1gb sdk) or there is a driver problem or you can try running cmd as administrator instead
Click to expand...
Click to collapse
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Montezz1 said:
I did try adb from the SDK that you've mentioned and have had the same results.
I also run in Administrator every time.
What I have just noticed with regards to the drivers is the change in the name of the device in device manager. Previously it showed as "Android Composite ADB Interface" but now it is showing as "Android Bootloader Interface".
I believe that might just be because the watch is stuck on the bootloader menu so that is how it is displayed, but it could be the cause.
Click to expand...
Click to collapse
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Xmaster24 said:
Your pc seems to be having trouble writing anything to the watch so if it is not the sdk then it must be your driver or bootloader
---------- Post added at 12:49 PM ---------- Previous post was at 12:43 PM ----------
Just checked the tool and it shouldn't do any harm at all to your watch unless you tried the bootloader lock so it must be your drivers
Click to expand...
Click to collapse
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Montezz1 said:
Hi there,
I've just tried to update the drivers but they seem to be up to date.
Yeah, the only reason I thought the program had done some damage is because it froze which resulted in getting stuck on the fastboot menu, but you've more knowledge so I guess that's not the issue.
I'm not entirely sure what else can be done here. I think I might have to just get another watch and stop the update as that is when all the problems occurred.
If you can think of anything else to try, I would be willing to give it a go but don't worry yourself too much if you're out of ideas.
I really appreciate your help up to this point anyways
Thanks
Click to expand...
Click to collapse
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Xmaster24 said:
Try and lock your watch with
fastboot oem lock
then try again with
fastboot oem unlock
Also when was the first time you flashed anything anyway?
Click to expand...
Click to collapse
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Montezz1 said:
I was able to lock and then unlock, and the device notified me that it was erasing, but when I try to start the device, it still brings be back to the fastboot menu.
Do you mean flashing devices in general or flashing this specific device?
Click to expand...
Click to collapse
This device I just want to know if you ever actually successfully flashed anything to this device
Xmaster24 said:
This device I just want to know if you ever actually successfully flashed anything to this device
Click to expand...
Click to collapse
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Montezz1 said:
The first attempting of flashing anything to this device I believe was when using the Return to Stock tool.
I choose the "Install ROM" option which I can see from the script attempts to flash.
So I guess it's never been successful on this device.
Click to expand...
Click to collapse
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Montezz1 said:
This whole problem started due to the fact that I couldn't see the device using ADB, so I tried to look for a method to solve that which then caused the problem I'm having now.
The only variable I can put it down to is an update that was pushed to the watch as prior to that, I had no problems at all.
Click to expand...
Click to collapse
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Xmaster24 said:
Yup sounds like a driver problem for sure uninstall the watch drivers and download the google drivers here
Click to expand...
Click to collapse
I do not believe it...
After all of this, it was the drivers...
I don't get it though!! I tried to reinstall them before and nothing changed!
It's only when I completely deleted them and reinstalled that it worked.
Honestly dude, thank you so much for your help and patience. My watch is now working and paired with my phone.
I'm waiting for it to sync but hopefully I will be able to run ADB and all will be well again
Thanks you so much again.