If anyone has picked up the new LG Optimus Fuel #LGL34C , & doesn't know, it CAN be rooted. I picked up one at Wal Mart last week for $30. I mean, a dual-core Kit Kat 4.4 LG device for $30 - I couldn't pass it up for Dev purposes. Now if I could only unlock the bootloader, lol. It doesn't even boot into Recovery, Bootloader, Download, or Fastboot. I'm sure someone will break it wide open soon.
http://www.androidarea51.com/all-things-root/working-root-for-lg-optimus-fuel-woot/
man lets hope so i was first to get the right mod string for it on towelroot v3 but no luck on bootloader yet im hoping it gets sorted out soon. i did pull the recovery.img directly from the phone and it does have a recovery but it just doesnt work for some reason.
Yes, I've been trying all kinds of methods, but none of them seem to work. Since the phone is so new, there's not much activity surrounding it, but we will see.
toxinburn said:
man lets hope so i was first to get the right mod string for it on towelroot v3 but no luck on bootloader yet im hoping it gets sorted out soon. i did pull the recovery.img directly from the phone and it does have a recovery but it just doesnt work for some reason.
Click to expand...
Click to collapse
Tagging along because I picked up one of these from Walmart over the weekend. My main phone went missing and I needed to get something going quickly. Couldn't believe they had an Android 4.4 device for $30. Of course if it could be rooted and some custom ROM's be loaded I'd love to tinker with it.
Stock Firmware
Has anyone been able to find a stock firmware for lgl34c or does anyone have a backup of one
ravenmore said:
Tagging along because I picked up one of these from Walmart over the weekend. My main phone went missing and I needed to get something going quickly. Couldn't believe they had an Android 4.4 device for $30. Of course if it could be rooted and some custom ROM's be loaded I'd love to tinker with it.
Click to expand...
Click to collapse
It CAN be rooted. Using towel root mod strings.
@ravenmore Yes, like toxinburn said, it CAN be rooted. Just follow the link in the OP. Make sure you change the numbers as described in reply #1 of the post. Have any questions, just reply here, or PM me. Good luck. @bigneo1973 I haven't found a stock yet, & my device is semi-bricked right now. They're making progress at this thread - http://www.forum.xda-developers.com/showthread.php?t=2791871 Good luck
hey skyline i see you softbricked when you plug the phone in does it come up with two folders verinfo and image? If so I may be able to help you. If that is the case it is in qualcomm bulk mode and you can use linux to push the original files back to it, I messed up my aboot and was able to repair it thru linux......http://forum.xda-developers.com/showthread.php?t=2426426 read this it should help if you need any working img files let me know.
skyline247 said:
@ravenmore Yes, like toxinburn said, it CAN be rooted. Just follow the link in the OP. Make sure you change the numbers as described in reply #1 of the post. Have any questions, just reply here, or PM me. Good luck. @bigneo1973 I haven't found a stock yet, & my device is semi-bricked right now. They're making progress at this thread - http://www.forum.xda-developers.com/showthread.php?t=2791871 Good luck
Click to expand...
Click to collapse
---------- Post added at 11:53 PM ---------- Previous post was at 11:51 PM ----------
skyline247 said:
@ravenmore Yes, like toxinburn said, it CAN be rooted. Just follow the link in the OP. Make sure you change the numbers as described in reply #1 of the post. Have any questions, just reply here, or PM me. Good luck. @bigneo1973 I haven't found a stock yet, & my device is semi-bricked right now. They're making progress at this thread - http://www.forum.xda-developers.com/showthread.php?t=2791871 Good luck
Click to expand...
Click to collapse
I forgot to say also that the link to thread you posted doesnt work.
toxinburn said:
I forgot to say also that the link to thread you posted doesnt work.
Click to expand...
Click to collapse
This is most likely the thread he was referring to
Has anyone been able to get WiFi tether to work on this phone?
I've tried a bunch of different versions of WiFi tether for root users, with a variety of different settings. Usually I get tethering started with errors, but the log file is always blank.
Edit: I've gotten as far as being able to see the network in ad-hock mode. But can't connect to it from my computer.
Update:
I bought WiFi Tether Router in the playstore. Works great.
found bootloader
toxinburn said:
man lets hope so i was first to get the right mod string for it on towelroot v3 but no luck on bootloader yet im hoping it gets sorted out soon. i did pull the recovery.img directly from the phone and it does have a recovery but it just doesnt work for some reason.
Click to expand...
Click to collapse
after running towelroot and supersu i installed rashr and it has the option to boot into bootloader and recovery
Hey I have a rooted LG Optimus Fuel and I think I did something to break the WiFi because it won't turn back on at all.. I downloaded MAC Spoofer and changed my MAC address one time then changed it back to default and ever since then WiFi would not turn back on at all.. Im only posting here because this is a fairly new phone and this thread seems to have the most activity about this device.. Please if anyone has any ideas it would be greatly appreciated.
Sent from my LGL34C using XDA Free mobile app
qw3rty3 said:
Has anyone been able to get WiFi tether to work on this phone?
I've tried a bunch of different versions of WiFi tether for root users, with a variety of different settings. Usually I get tethering started with errors, but the log file is always blank.
Edit: I've gotten as far as being able to see the network in ad-hock mode. But can't connect to it from my computer.
Update:
I bought WiFi Tether Router in the playstore. Works great.
Click to expand...
Click to collapse
Any Special Settings you used?
LGL34C WiFi Tether
ellisgeek said:
Any Special Settings you used?
Click to expand...
Click to collapse
I have been trying for days to get tethering working. Any help for me guys? I've tried just about every tethering app out there. Thanks in advance.
scangd said:
I have been trying for days to get tethering working. Any help for me guys? I've tried just about every tethering app out there. Thanks in advance.
Click to expand...
Click to collapse
I use Barnacle Wifi Tether, you can download it from the play store. Sometimes it gets hung up and you have to stop and start it again. Other than that it works for me. Would like to see some custom roms and recovery soon for this phone. seems like it has alot of potential.time will tell..
I seem to have accidentally "repurposed" my home button to something else while I was fooling with a /system file. If someone could help that would be great. Even if it was an attacment of a copy of the stock /system folder and all of its sub(directories/folders/files). Actually that would be preffered.
Either way, any and all help is appreciated.
Quickdraw996
Sent from my LGL34C using XDA Free mobile app
Quickdraw996 said:
I seem to have accidentally "repurposed" my home button to something else while I was fooling with a /system file. If someone could help that would be great. Even if it was an attacment of a copy of the stock /system folder and all of its sub(directories/folders/files). Actually that would be preffered.
Either way, any and all help is appreciated.
Quickdraw996
Click to expand...
Click to collapse
Never mind, I just bought a new one for $20 at Walgreens.
Sent from my LGL34C using XDA Free mobile app
Hi. Can someone confirm this for me? Does this phone, LG Optimus Fuel, use a battery labeled as "LG BL-44JH"?
goldentequila said:
Hi. Can someone confirm this for me? Does this phone, LG Optimus Fuel, use a battery labeled as "LG BL-44JH"?
Click to expand...
Click to collapse
Mine does. However it is a net10 variant, I cannot confirm nor deny that any other variants, such as Straight Talk, does or does not have that model number on the battery.
Sent from my LGL34C using XDA Free mobile app
LG Optimus Fuel L34C - How To Add Your Own Ringtones
LG Optimus Fuel L34C - How To Add Your Own Ringtones
.
How to add your own MP3 ringtones to a LG Optimus Fuel L34C phone from a Windows PC. This will also probably work on most other LG android smartphones, but I haven't tried it.
.
Any MP3 file can be used as a ringtone, even a whole song. There is no limit to the file size.
.
.
Plug USB data cable into the Windows PC USB port. You can use the charger cable for this, once you disconnect it from the charger plug (If it is the type that unplugs from the charger plug, otherwise you will need a USB to micro-USB data cable).
.
Plug micro USB cable end into L34C phone (The L34C phone should be turned on and on the main screen).
.
Wait for the "Select USB Connection Method" screen to come up on the L34C phone. Choose "Media Sync (MTP)".
.
-On the Windows PC, start the Windows File Explorer.
-Go to the top of the menu tree in Windows File Explorer and select "My PC" or "This PC"
-On the right window pane, next to the C: drive icon, a phone icon should appear with the name of your phone. Double-Click on it.
-Now you should see two selections for the L34C phone, "internal storage" and "SD card". Double-Click on "SD card".
-If there is an "Android" folder, click on it. Otherwise, create a folder called, "Android" (without the quotes).
-Inside the "Android" folder, create a folder called, "media" (without the quotes).
-Inside the "media" folder, create a folder called, "ringtones" (without the quotes).
-Inside the "ringtones" folder, create a folder called, "audio" (without the quotes).
.
The finished folders should look like this (Uppercase and lowercase letters should also match):
.
/Android/media/ringtones/audio/
.
Add any MP3 ringtone files to the "audio" folder you have created on the SD card.
.
.
When finished, disconnect the data cable from the L34C phone.
.
If you go to your phone ringtones list on the LG phone, your added ringtones should appear at the top of the list under "MY RINGTONES", above the "LG RINGTONES" list.
Related
Can anyone help me get my TABLET S (non-XPERIA) back to the pre-Revision 5 release of 4.0.3?
I HATE, HATE, HATE R5. Took away so many things that I was using, and I want to go back.
I already called SONY and was told I can't go back. I told the guy...I will find a way - and hung up.
I am sure it can be done....just need to find the software and the steps to do it.
bearhntr
bearhntr said:
Can anyone help me get my TABLET S (non-XPERIA) back to the pre-Revision 5 release of 4.0.3?
I HATE, HATE, HATE R5. Took away so many things that I was using, and I want to go back.
I already called SONY and was told I can't go back. I told the guy...I will find a way - and hung up.
I am sure it can be done....just need to find the software and the steps to do it.
bearhntr
Click to expand...
Click to collapse
Simple as. Change vendor/vendor.prop incremental to a lower number and flash an older update.zip
Or use AIO and install rescue back door, boot loop protection.
Manually flash either 120803002 or 120410004.zip
Done
stifilz said:
Simple as. Change vendor/vendor.prop incremental to a lower number and flash an older update.zip
Or use AIO and install rescue back door, boot loop protection.
Manually flash either 120803002 or 120410004.zip
Done
Click to expand...
Click to collapse
While I appreciate the reply, which gives you credit for a post (yes - I know how these forums work), I asked for the steps and software. I know it can be done, as I did it to my DroidX phone and had someone give me step by step instructions (rather directed me to a post he had done a year before with had everything I needed in one place).
I am talking real steps 1)...2)...3)... and links to the files. Not just some partial filenname which sends me on a goose chase.
Someone in another forum directed me to download signed-nbx03_001-ota-120410004.zip but then gave me nothing more - like do I put it on an SD CARD and do something with it. How do I get into BootLoader mode so that I can apply it, etc. I have already paid for a couple of apps that I used when I did my phone - I am sure that they might work for my tablet as well.
I am no idiot, do not need Crayola drawings, but at least 6th grade steps and locations on how to do this.
I cannot believe that for $350.00 that I just paid for the table SONY would tell me you can't do it - nor do they offer a manner to go back to the previous level (1 step) if you do not like the ROM that got installed.
4.0.3 (r5) is for the birds....takes away some of the best features of the reason I bought the SONY Tablet S over something else.
While I do appreciate, and do thank/reward those that help me - I think I need a little more than a simple 3 line response.
Curtis
bearhntr said:
While I appreciate the reply, which gives you credit for a post (yes - I know how these forums work), I asked for the steps and software. I know it can be done, as I did it to my DroidX phone and had someone give me step by step instructions (rather directed me to a post he had done a year before with had everything I needed in one place).
I am talking real steps 1)...2)...3)... and links to the files. Not just some partial filenname which sends me on a goose chase.
Someone in another forum directed me to download signed-nbx03_001-ota-120410004.zip but then gave me nothing more - like do I put it on an SD CARD and do something with it. How do I get into BootLoader mode so that I can apply it, etc. I have already paid for a couple of apps that I used when I did my phone - I am sure that they might work for my tablet as well.
I am no idiot, do not need Crayola drawings, but at least 6th grade steps and locations on how to do this.
I cannot believe that for $350.00 that I just paid for the table SONY would tell me you can't do it - nor do they offer a manner to go back to the previous level (1 step) if you do not like the ROM that got installed.
4.0.3 (r5) is for the birds....takes away some of the best features of the reason I bought the SONY Tablet S over something else.
While I do appreciate, and do thank/reward those that help me - I think I need a little more than a simple 3 line response.
Curtis
Click to expand...
Click to collapse
If you KNEW these forums you would know that we do not take kindly to those who do not use the SEARCH function. It is there so we don't have to repeat ourselves over and over again.
None the less.
If you can't manage this then take it in to Sony saying that you are having issues with the camera (they will restore it to original 3.2 software)
Step One
Root your device.
See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step Two
Use AIO to 'Install "rescue-backdoor" [anti-bootloop protection].'
First you want to download, then extract to a folder, then double-click on S.onyTablet.S.bat, this will open a menu, enter '4' then press enter then enter '1' and press enter again. MAGIC, you have now decreased your incremental, well done.
Step 3
See my Update Links NOTE: ALSO IN MY SIGNATURE AND HAS BEEN FOR A LONG TIME, others had no problem with it
Find the update you require to flash, you want signed-nbx03_001-ota-120803002.zip or for you highness LINK
Step 4
Copy signed-nbx03_001-ota-120803002.zip to your SD card. Google how to if you don't know
Step 5
Put SD card back into tablet and boot into recovery. See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step 6
Leave tablet to boot into R1A
Step 7
Be happy and click the fricken Thanks button.
P.S this is not hard stuff
Stifilz,
Thank you so very much for the long post. I was going cross-eyed looking for something like that...surprised that no-one has STICKY'd that one.
So I checked out #1 - followed the directions in FAQ to put the ADB path into the my DOS PATH statement (ahhhhh. the good old days - DOS). I can go to the DOS prompt and type 'adb' from any directory and it will bring up the ADB menu - hence it is working.
So I went to the task manager and verified that ADB.EXE was not listed. I typed ADB DEVICES (lower case) and it gave me the following:
C:\Windows\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Windows\system32>:
I made sure that the SONY TABLET is seen - I unplugged from the computer and re-plugged, Windows bonks and wants to know if I want to browse the device. I have made sure the USB DEBUGGING is enabled on the device (before I connect it - had that problem with my DROIDX). Still the ADB 0.29 is not seeing the SONY TABLET S.
Any Ideas why?
When I try running the RUNME.BAT file I get the following:
D:\ROOT_W_RESTORE>runme
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (02.10.2012) v13 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
x) Unroot
Make a choice: 2
Special mode:
1) Root
2) Rollback
Make a choice: 1
Tablet S mode enabled!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
and it just sits there...left it for 20 minutes while I was making dinner. Should I have the power plugged in at the same time? Do I need to enable the STAY AWAKE setting?
Your guidance is again requested.
Please ignore my previous response. I really am not an ass - I was getting frustrated during my 2+ hours search not finding a message such as yours with the steps laid out like that - without making you bounce from one post to another - to another, it was like a scavenger hunt.
Again accept my thanks and my apologies.
Have you installed the drivers http://forum.xda-developers.com/showthread.php?t=1488822
Sent from my Desire S using xda app-developers app
gordo79 said:
Have you installed the drivers http://forum.xda-developers.com/showthread.php?t=1488822
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
Hey...THANKS. not sure why I did not catch that the tablet did not show as adb device, as I had to do the same thing when I rooted my DroidX...I guess I assumed that it would do it from that install.
Again thanks...now lets see if I can get the 4.0.3 (pre-R5) back on the tablet.
SO FAR SO GOOD. Weird that the SD card does not show from the tablet with it in the SD slot on the tablet like it does on my DROIDX. You can copy files to and from the SD Card in the phone without taking it out.
See...you can teach an old bear new tricks.
Stifilz,
On last step of your instructions...have one question.
What is the difference between this signed-nbx03_001-ota-120803002.zip that you mention and the signed-nbx03_001-ota-120410004.zip that I also downloaded from another forum message I was reading?
Thanks
bearhntr said:
Stifilz,
On last step of your instructions...have one question.
What is the difference between this signed-nbx03_001-ota-120803002.zip that you mention and the signed-nbx03_001-ota-120410004.zip that I also downloaded from another forum message I was reading?
Thanks
Click to expand...
Click to collapse
120803 is 2012-Aug-03 which is ICS R1A
120410 is 2012-Apr-10 which is ICS original. R1A is suposedly better
Stifilz
stifilz said:
120803 is 2012-Aug-03 which is ICS R1A
120410 is 2012-Apr-10 which is ICS original. R1A is suposedly better
Stifilz
Click to expand...
Click to collapse
stifilz,
Well I was successful...but it killed my ROOT. I got to playing with the new load, and it looks to have kept a bunch of my apps and some settings, but some of the apps do not work well.
I take it that if I go though the process again and choose to NOT RESTORE, it will put it back to OUT OF BOX configuration?
I do not have a lot of customizations that I will have a problem re-doing to get it back to O-O-B configuration. All of my apps can be pulled back off GOOGLE PLAY. Learning that is advantageous to have a GOOGLE PLAY account for each device (he he).
There are a lot of apps that I have noticed on GOOGLE PLAY that say not compatible with my device. Any known reason why? I figured that open source was open source.
I saw in the AIO that you can change the device type of your tablet to something else. Have you ever tried that? Does it seem to work?
I have also read that the UK models have a slot for a SIM card. Do you know if the US models have it to - just maybe inside and inaccessible?
I am loving the tablet....but find that now that I am back on the 4.0.3 my media files on my HTPC will not play. I find this wierd. The 4.0.3 update - according to the SONY site, says it improves the H.264 file playing...and nothing is mentioned about any changes in the R5 update.
Also one thing I noticed about the R5 load was it would sometimes just turn OFF the tablet. No reason or rhyme to it. Ever hear of that?
I may wind up going back up - if I cannot get them to play...have yet to try copying one to the SD card and playing it. But all of them used to play before I went back down.
Been looking into codecs too - but most of the processing of streamed DLNA stuff is done on the host machine [ putting on the Sherlock Holmes outfit again ]
Thank again for all your insight.
bearhntr said:
stifilz,
Well I was successful...but it killed my ROOT. I got to playing with the new load, and it looks to have kept a bunch of my apps and some settings, but some of the apps do not work well.
I take it that if I go though the process again and choose to NOT RESTORE, it will put it back to OUT OF BOX configuration?
I do not have a lot of customizations that I will have a problem re-doing to get it back to O-O-B configuration. All of my apps can be pulled back off GOOGLE PLAY. Learning that is advantageous to have a GOOGLE PLAY account for each device (he he).
There are a lot of apps that I have noticed on GOOGLE PLAY that say not compatible with my device. Any known reason why? I figured that open source was open source.
I saw in the AIO that you can change the device type of your tablet to something else. Have you ever tried that? Does it seem to work?
I have also read that the UK models have a slot for a SIM card. Do you know if the US models have it to - just maybe inside and inaccessible?
I am loving the tablet....but find that now that I am back on the 4.0.3 my media files on my HTPC will not play. I find this wierd. The 4.0.3 update - according to the SONY site, says it improves the H.264 file playing...and nothing is mentioned about any changes in the R5 update.
Also one thing I noticed about the R5 load was it would sometimes just turn OFF the tablet. No reason or rhyme to it. Ever hear of that?
I may wind up going back up - if I cannot get them to play...have yet to try copying one to the SD card and playing it. But all of them used to play before I went back down.
Been looking into codecs too - but most of the processing of streamed DLNA stuff is done on the host machine [ putting on the Sherlock Holmes outfit again ]
Thank again for all your insight.
Click to expand...
Click to collapse
If you use MX player it will play most files. Regarding the apps have you checked the unknown sources in the settings?
Sent from my Desire S using xda app-developers app
bearhntr said:
Hey...THANKS. not sure why I did not catch that the tablet did not show as adb device, as I had to do the same thing when I rooted my DroidX...I guess I assumed that it would do it from that install.
Again thanks...now lets see if I can get the 4.0.3 (pre-R5) back on the tablet.
Click to expand...
Click to collapse
bearhntr, I have been struggling trying to get my tablet to show up when I type in adb devices. I was having the same problem you had before you wrote this post. I followed the directions in Bluechips post for the ADB installer (very huge thanks for all those who develop these things to make it easier) and even did step by step with the video. I have also tried other methods to get ADB to work.
Long story short, did you do anything different than listed in Bluechips post to achieve success in getting your computer to see your tablet as an ADB device?
Thanks!
esonnen said:
bearhntr, I have been struggling trying to get my tablet to show up when I type in adb devices. I was having the same problem you had before you wrote this post. I followed the directions in Bluechips post for the ADB installer (very huge thanks for all those who develop these things to make it easier) and even did step by step with the video. I have also tried other methods to get ADB to work.
Long story short, did you do anything different than listed in Bluechips post to achieve success in getting your computer to see your tablet as an ADB device?
Thanks!
Click to expand...
Click to collapse
Esonnen,
I followed the steps from BLUECHIPS direction step by step. Are you seeing the tablet at all in the Windows Device manager? Mine was showing up in the device manager - but not correctly until I installed the drivers.
I right mouse button clicked on the SONY TABLET S entry in the device manager in Windows and chose UPDATE DRIVER...then pointed it to the extracted AdbWinUsbApi.dll file. Followed the prompts and after that the SONY TABLET was listed in an new CATEGORY called ANDROID PHONE, as ANDROID COMPOSITE ADB INTERFACE.
I found that if I did not get it to show as this in the DEVICE MANAGER, nothing I tried with ADB or other tools that used that software would work. This was the same problem I had when I was working with my DROIDX. I had thought that by getting the DROIDX to work properly in the rooting process - that the tablet would as well. It was the simple act of changing the driver to the AdbWinUsbApi.dll that fixed it.
gordo79 said:
If you use MX player it will play most files. Regarding the apps have you checked the unknown sources in the settings?
Sent from my Desire S using xda app-developers app
Click to expand...
Click to collapse
I had already tried that player and it also downloaded the ARMv7 CODEC set to the tablet.
This player may work fine...but it wants the files to be LOCAL to the device or streamed from a WEBPAGE type arena.
I want something that will stream DLNA (the tablet sees all three of my Windows DLNA device and my Sony STR-DN1020 receiver) using the DLNA services that are in 4.0.3. It even shows me the folders on my HTPC. I can also list the movies on it. Where the 4.0.3(r5) showed an actual thumbnail of the first frame of the .M4V files - the 4.0.3 shows what appears to be a set of hotair balloons.
Touching one of the files yields the following error: "INVALID MEDIA - PLAYBACK NOT SUPPORTED" These files play fine on the HTPC and my D-LINK DSM-750 Media Center Extender (and in 5.1 audio). Generally with DLNA the decoding is handled at the source PC, not the playback device. I find this weird too.
Maybe I will try copying one of these files to the device and try playing it from there....try and narrow it down.
GORDO79,
Not sure what has happened, but my Tablet S is now playing the videos from my HTPC. The details of all the videos hows VIDEO CODEC: UNKNOWN and AUDIO CODEC: UNKNOWN, but all of them seem to be playing.
I searched the GOOGLE PLAY STORE, but do not find any codecs listed there other than the ones for various players.
I am so happy now that I can play my videos and I think I will be able to THROW them to my DSM-750 (Media Center Extended) until I can get a BRAVIA TV (hint hint Santa).
Much thanks for everyone's help.
stifilz said:
If you KNEW these forums you would know that we do not take kindly to those who do not use the SEARCH function. It is there so we don't have to repeat ourselves over and over again.
None the less.
If you can't manage this then take it in to Sony saying that you are having issues with the camera (they will restore it to original 3.2 software)
Step One
Root your device.
See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step Two
Use AIO to 'Install "rescue-backdoor" [anti-bootloop protection].'
First you want to download, then extract to a folder, then double-click on S.onyTablet.S.bat, this will open a menu, enter '4' then press enter then enter '1' and press enter again. MAGIC, you have now decreased your incremental, well done.
Step 3
See my Update Links NOTE: ALSO IN MY SIGNATURE AND HAS BEEN FOR A LONG TIME, others had no problem with it
Find the update you require to flash, you want signed-nbx03_001-ota-120803002.zip or for you highness LINK
Step 4
Copy signed-nbx03_001-ota-120803002.zip to your SD card. Google how to if you don't know
Step 5
Put SD card back into tablet and boot into recovery. See my FAQ LINKS IS ALSO IN MY SIGNATURE!!
Step 6
Leave tablet to boot into R1A
Step 7
Be happy and click the fricken Thanks button.
P.S this is not hard stuff
Click to expand...
Click to collapse
stifilz,
Again many thanks for your help with this. Not sure why the ROOT broke when I did the deed (and I was successful), but I tried to get my root back following your steps again (other than flashing with the .ZIP from the SD card), and I cannot seem to get my ROOT back. Neither the AIO or the ROOT W/RESTORE works.
I wanted to use the AIO to turn off the OTA prompt and run a few of the tweaks, but each time I run it - the screen goes red and tells me I have to ROOT.
Any ideas where I am going wrong?
Much Thanks
can anyone tell me the main differences between the first ics release and the r1a?
sony tablet s 4.0.3 r5?
Personally I know that many people come to know about looking for it and I've spent hours and hours looking for a way to rooted my tablet and still nothing ...
Really there is still no way to update the sony tablet s 4.0.3 r5?
Nor has the downgrade to another rom?
I've looked almost everywhere but to no avail. help me.
I have been able to get the update tool software to flash the kdz file and I over right the bin in the process.
The phone flashes fine. But, after flashing I still have no root at all. I'm following every step by step instruction.
dismantlehands said:
I'm so happy that the Lelus Root method works. But, not for me. I have no other machine to use this method on that does not run windows 8.
When I attempt to put the phone in Software update mode when trying to flash the kdz file, windows 8 crashes because of driver issues. Has anyone else had this issue? Or could maybe point me in the right direction into fixing this so i can obtain root for my L9? :highfive: Team work guys, team work. *self five*
Click to expand...
Click to collapse
Works perfect on Windows 8. Mine too and one more user confirmed it before me.
Not even this, Since 5000+ years for hair growing medicine also, they always said "RESULTS MAY VARY" lolz
hey, listen! lol
cmahendra said:
Works perfect on Windows 8. Mine too and one more user confirmed it before me.
Not even this, Since 5000+ years for hair growing medicine also, they always said "RESULTS MAY VARY" lolz
Click to expand...
Click to collapse
Just sent you a pm asking about this issue. Sorry for not having any patience.
since that is the case, im even more confused now than ever.
I have tried uninstalling drivers and everything, still crashes. Fresh install is not an option seeing I have no way to backup my data.
dismantlehands said:
Just sent you a pm asking about this issue. Sorry for not having any patience.
since that is the case, im even more confused now than ever.
I have tried uninstalling drivers and everything, still crashes. Fresh install is not an option seeing I have no way to backup my data.
Click to expand...
Click to collapse
Not sure the situation of your window 8 and no one can help you without proper details, but my friend, in my humble opinion your title "[Q] Lelus root method crashes windows 8" is sort of misleading and may be scaring people from using Lelus method. It sounds like you are telling people that "Lelus root method crashes windows 8, so dont use it."
Make it "[Q] Please help! Why Lelus root method is not working on my windows 8?" to be more precise.
Are sure your clicking the network test flash button? Do not click the start button right under the kdz browser folder thing. There should be a button on the lower right hand. Also run the prgram in compatibility as administrator.
Virusbetax said:
Are sure your clicking the network test flash button? Do not click the start button right under the kdz browser folder thing. There should be a button on the lower right hand. Also run the program in compatibility as administrator.
Click to expand...
Click to collapse
+1 good point. You are talking about this http://forum.xda-developers.com/showpost.php?p=38914794&postcount=117
Virusbetax said:
Are sure your clicking the network test flash button? Do not click the start button right under the kdz browser folder thing. There should be a button on the lower right hand. Also run the prgram in compatibility as administrator.
Click to expand...
Click to collapse
My laptop crashes right after it tries to detect the L9 running in SW mode. So, I do not even get as far as the program it self.
I appreciate the input Virusbetax.
dismantlehands said:
My laptop crashes right after it tries to detect the L9 running in SW mode. So, I do not even get as far as the program it self.
I appreciate the input Virusbetax.
Click to expand...
Click to collapse
my win8 laptop has a few runtime errors during the flashing process itself, and I have to reboot afterwards, but never something as bad as this. you may be experiencing other problems not related to this phone.
may not be the BEST solution but you could always download tinyXP and virutalbox and try everything in a virtual machine..........
Yea there also virtual xp you can use. I believe is from windows website. Try with cousins or friends computer? Maybe theres will work.
Re: [Q] Lelus root method crashes windows 8
Have you tried other cables? Have you used the other usb ports on your system? Have you checked device manager on your laptop to see if there are other devices with errors? Have you gone to your manufactures Web site to see if there are new drivers or an updated bios?
Sent from my LG-P769 using xda premium
psychoace said:
Have you tried other cables? Have you used the other usb ports on your system? Have you checked device manager on your laptop to see if there are other devices with errors? Have you gone to your manufactures Web site to see if there are new drivers or an updated bios?
Sent from my LG-P769 using xda premium
Click to expand...
Click to collapse
Switching it from the usb 3.0 port to the 2.0 port worked. I successfully got the phone in s/w mode to run with the software update tool. After the tool finishes my phone reboots. Still no root..... I am following every step....
Its all Security and Compatibility issue. Yesterday, I have done some changes in my Root Guide.
======================
2) Download Root_and_Flash_Guide_byCMahendra(date).zip file (attached with this post) and extract in your C-Drive.
Now you will get three folders named "C:\RootLelus" and "C:\RootFlash" and "C:\shttps"
If these folders need any permissions you should provide in folder security section by adding user "everyone" or "<yourname>" and give full access. (example video) This is Optional and should be done if you have permission errors while flashing. Do it for all three folders.
==================
Also run EXE files with WindowsXP compatibility mode and Run As Administrator, if any trouble. In fact I never did this. Just a suggested workaround.
STILL NOTHING IS GUARANTEED AND MAY NOT WORK FOR YOU.
Do some trial and error and you tell us.:good:
cmahendra said:
Its all Security and Compatibility issue. Yesterday, I have done some changes in my Root Guide.
======================
2) Download Root_and_Flash_Guide_byCMahendra(date).zip file (attached with this post) and extract in your C-Drive.
Now you will get three folders named "C:\RootLelus" and "C:\RootFlash" and "C:\shttps"
If these folders need any permissions you should provide in folder security section by adding user "everyone" or "<yourname>" and give full access. (example video) This is Optional and should be done if you have permission errors while flashing. Do it for all three folders.
==================
Also run EXE files with WindowsXP compatibility mode and Run As Administrator, if any trouble. In fact I never did this. Just a suggested workaround.
STILL NOTHING IS GUARANTEED AND MAY NOT WORK FOR YOU.
Do some trial and error and you tell us.:good:
Click to expand...
Click to collapse
The 7th try i had to run every single exe in administrator mode. So, for me. His updated method did indeed work for me. Thanks dude.
dismantlehands said:
The 7th try i had to run every single exe in administrator mode. So, for me. His updated method did indeed work for me. Thanks dude.
Click to expand...
Click to collapse
Glad it helped.
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Tyetiger said:
Is there a mod that allows me disable the Installer from automatically coming up when connecting to a pc through USB?
Click to expand...
Click to collapse
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Itsmyphoneyo said:
I was able to by deleting autostart.iso file from \system\etc
I use Mac and it no longer mounts the mobile Verizon app. I assume its the same for windows.
Click to expand...
Click to collapse
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Tyetiger said:
Ive been trying for days! Haven't been able to find that folder or file. Unfortunately I have a PC
Click to expand...
Click to collapse
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
I see autorun.iso, I assume that's what you're referring?
Sent from my SCH-I545 using xda app-developers app
Itsmyphoneyo said:
You need root to do this... I probly should have mentioned that. Sorry. Getting root is easy now, there are a could threads on how to root with very easy step by step instructions. After you gain root, purchase root explorer from PlayStore (yes, you have to spend a couple $ but its worth it) and use that app to navigate and delete the file. You will likely use the app again, unless you switch to an iPhone. So it's worth the little bit of money.
Click to expand...
Click to collapse
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Tyetiger said:
Ok. I was able to download a root explorer and remove the autorun.iso. But I notice the phone still says "Installer is connected" and I still can't view the sdcard or drive on the phone unless I'm in Camara(PTP) mode.
Click to expand...
Click to collapse
Check your usb debugging settings. you might need to either check that box or unchecked it. I can't help much more than that if you're using Windows, I'm a mac user. But that sounds like all you would need to do. Hope it helps.
Verizon installer
Okay here is a weird one (or maybe not). Started getting this when I first connected the S4 to PC via USB. Now when I connect my S3 I am getting the same popup. S3 is rooted never had this message.
I am thinking this is somehow embedded into the new Samsung USB drivers. When the phone is plugged in, some form of check reveals a VZW phone which triggers the installer????
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Bump, I'd like to know the same thing.
ecen92 said:
Bump, I'd like to know the same thing.
Click to expand...
Click to collapse
I'm getting connect/disconnect every 3 seconds.
Gam3r 4 Life said:
Did anyone figure this out? I was able to stop the Verizon Installer Pop up by renaming the autorun.iso, but there is still a 30 second delay before I get access the the phones internal and external memory.
Click to expand...
Click to collapse
Still trying to figure this one out........any ideas......anyone????
Zelmo88 said:
Still trying to figure this one out........any ideas......anyone????
Click to expand...
Click to collapse
Bump! Anyone find a cure for this yet?
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
desertopal said:
Tried this on Sophisticated 2.5 . It's a 4.3 rom I get this: error: device offlineerror: device offline even though Link Status is Device Connected. My autorun.iso file was in /system/etc I renamed it. Changing the dialer code *#0808# to MTP works until I reboot. Same thing with dialer code *#7284#. I edited a file in /efs/carrier/HiddenMenu "OFF" changed to "ON" all in capital letters This survives a reboot.
But MTP doesn't
Click to expand...
Click to collapse
I'm on MK2 rooted and I have the same problem with the setting not surviving a reboot. Anyone have any other ideas?
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
CovXX said:
Removing the file should work, if it's giving you a delay then my guess is either your computer or the device is trying to find the file. Back on my s3 and dna rom I had only removed the file and vzw installer didn't show up
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Zelmo88 said:
Removing the file does not solve the problem, it still connects as installer for a while before connecting as media device. It's not a huge problem, just annoying! I'm curious if everyone has this problem, or if it's just a few of us??
Click to expand...
Click to collapse
I have the same issue. I've tried looking through/changing settings in build.prop, default.prop and init.usb.rc with no luck. I need to do a little more searching to better understand init.usb.rc as a lot of the settings are jibberish to me.
Chris000001 said:
I think I figured it out. I'm still on original MDK build. I don't know if that changes anything.
1. autorun.iso removed (may not be necessary, but mine is gone)
2. enable hidden menus (step 2) http://forum.xda-developers.com/showthread.php?t=2303905
3. enter dialer code *#0808#
4. select MTP+ADB
5. reboot (may not be necessary)
My phone originally had nothing selected. I don't know how to go back to that unselected mode. I can't guarantee anything. It's working for me. My phone now connects in MTP mode within a second or two of connection (unless the phone is in the middle of a reboot, then that has to complete first.)
Click to expand...
Click to collapse
Running the Casual-gnote2 I get this: file/ Open Casual Script (go to location, click on the downloaded Casual-gnote2.jar) it opens and gives me this
Description for /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar
File Not Found Error: /home/wade/Downloads/CASUAL-GNOTE2-Hidden Menus.jar.txt
Delete this debug line in MenuItemOpenScriptActionPerformed()
If I just open Casual-gnote2 and click DO IT I get this: error: device offlineerror: device offline
In both cases the Link Status = Device Connected
Introduction
**EDIT**: Please see 4th post on how to obtain your MSL/SPC Code for the last step in restoring stock firmware
I figured it would be good to have a dedicated Factory Restore thread here for the LS990 (Sprint) G3 seeing as how we now have root and people want to be sure they can restore their phones if they screw something up.
First off, I am not presenting any new material here, I just simply gathered guides/tips/tricks from many forum members in an attempt to make it easier for LS990 users to restore their phones. Also, if you notice something wrong with the guide please say so! I have no ego here, we're all here to help one another so if I made a mistake please let me know
Hopefully this will be helpful to those who want to restore their phones back to stock and allow a thread for troubleshooting if someone is having issues
Disclaimer
I, nor anyone on XDA, is responsible for any damage done to your device. Please use at your own risk! The LG Flash Tool has the power to save your phone from a bootloop or soft-brick, however it can also do more damage if used improperly for the specified device. Please use with CAUTION.
Thank-You's/Credits
@wolfgart for hosting the stock G3 files. Please thank him in his thread here
@dokyson for his guide on how to restore the LG G2. Please thank him in his thread here
@AlanVenu for pointing out Sprint users should select "Board DL" in the LG Flash Tool. Please thank him at his post here
Team Codefire for finding an exploit that allows us to root our phones. Please thank (and donate if you can) to them here
Now lets get started!
Prerequisites
Sprint LG G3 (LS990)
Windows 7/8
LG Drivers (Links will be below)
Sprint LG G3 stock .tot file (Links will be below)
Sprint DLL file for LG Flash Tool (Links will be below)
LG Flash Tool (Links will be below)
A good/reliable USB cable
Backup your data! This will format your internal storage, including user apps, SMS/MMS, Call Logs, Pictures etc. So please backup your data
Downloads
Sprint LG G3 Stock LS990ZV4 .tot file
Sprint LG G3 DLL File
LG Drivers
LG Flash Tool
Generic LG G3 DLL (**ATTENTION!!! ONLY USE IF YOU EDITED THE BUILD.PROP TO A DIFFERENT PRODUCT MODEL/BUILD ID AND ARE STUCK IN A BOOTLOOP. USE THIS DLL INSTEAD OF THE SPRINT)<------Big Thanks to engine95 and autoprime
Steps
Download all files/zips above
Double click on the LGUnitedMobile exe to install the drivers
Extract the Setup_LGFlashTool.zip and double click on the exe inside the extracted folder to install the LG Flash Tool (note: make sure you don't choose a custom directory and that it installs to C:\LG\LGFlashTool)
Inside the extracted LG Flash Tool folder (where the exe is) there is a file called "MegaLock.dll". Copy this file and paste it in the C:\LG\LGFlashTool directory (overriding the current MegaLock.dll file)
If your phone is still working (and not in a bootloop or perpetually off) plug it in to your computer and let the installation of the LG Drivers finish (if your phone is in a bootloop or it won't turn off it shouldn't be a big deal)
Unplug your phone from your computer then turn off your phone
While its turning off you can open up the LG Flash Tool program (if no desktop icon was created for the program just do a search for it within your installed apps or browse for it from the start menu). You can open it with the default setting (Korea Factory)
Once your phone is completely powered off press and hold the Volume Up button and reconnect the phone to your computer via the USB while still holding the Volume Up button until you enter Download Mode (it will look like this)
Once you're in download mode let go of the Volume Up button and wait for the drivers to install on your computer
Once the drivers have finished installing navigate to your desktop and right-click on your Computer (or This PC) icon and select "Manage" (or do a search for "Device Manager")
In the Computer Manager screen select "Device Manager" then select Ports
Look for the LGE AndroidNet USB Serial Port (COM#) (where # just means whichever port is was installed to. Ex: (COM3)). Double Click on this and select "Port Settings"
Next, select "Advanced" then change the COM Port Number to COM41. Once COM41 is selected click OK, then OK again to save your settings. Now your Device Manager should have refreshed and the LGE AndroidNet USB Serial Port should have changed to (COM41). Exit out of Device Manager/Computer Manager.
Navigate to wherever you downloaded the LGLS990_20140704_LGFLASHv160_Download.zip and extract the zip.
Back in the LG Flash Tool Program the Model Config screen should be open. Select "Manual Mode". Right below it select the LGLS990_20140704_LGFLASHv160.dll you extracted for the DLL selection (navigate to wherever you extracted it)
After that select "Add" (immediately after the DLL selection option) and select the LS990ZV4_04.51101.tot file (navigate to wherever you downloaded it)
Now, navigate to Action Mode section and select Board DL. Click OK, then click the yellow arrow in the top left corner
After you click the yellow arrow (start) button the LG Flash Tool begins examining the DLL and tot file you selected. IF everything went OK after a little wait you'll see a "READY!!" prompt under the COM41 Port.
Once you see "READY!!" sign unplug your phone from the USB, wait 5 seconds, then plug your phone back into the USB
After you reconnected your device you'll notice the flashing process begins as indicated by the progress bar. It could take a while so just hang tight and keep an eye on the progress
Sometimes the LG Flash Tool will not show 100% progress but will successfully flash the firmware so keep an eye on your phone
Once the flash is finished (either indicated by 100% progress or the PASS sign that pops up) your phone will begin to reboot into the AAT Mini OS Screen. Once at the screen hold onto the power button and select "OK", then select the "normal boot (+power)" option
After that selection is made your phone should reboot normally
Sign into everything and let your phone settle for a few minutes. Then, restart the phone
If you're missing certain apps like WiFi Calling and Sprint Bloat please follow the links provided by @engine95 to restore these apps (I took apart the Sprint tot file and the apps are present, however for certain people these apps are not showing up immediately after the flash)
Success or Failure?
If your phone successfully rebooted into the system congrats! If not please look down for some trouble shooting tips (coming very soon! I need to hit the hay right now lol)
Again, I did not discover anything new, I thought it would be good to have a concise and detailed guide to restoring the LS990 to stock firmware. Hopefully this helps!
General Tips & Tricks to AVOID a Bootloop/Soft Brick
Stay away from editing the build.prop! Many users have reported that they made edits to the DPI, Build ID, Product Model. Then upon rebooting their phones they are in a boot loop. For right now, I'd say stay away from making any build.prop edits BUT if you do please have ADB ready along with the stock build.prop on your computer so you can troubleshoot
Have a backup ready! As of right now we don't have a custom recovery, however if you are modifying system files/apks make sure you have stock equivalents on your computer and ADB ready to troubleshoot
Only use mods/themes for the LS990 model. While the LS990 (Sprint) model certainly does share a lot of the same components as the international versions certain framework/system apps have certain Sprint/CDMA settings in them (ex: framework-res.apk, LGUSMms.apk, etc) so just be careful.
Use common sense. As of right now we don't have a custom recovery; but we will at some point. So just hold off for a little bit on hacking up your system environment.
Troubleshooting Tips if the Flash Failed
Check your USB Cable. I know it may seem silly, but if you don't have a stable/reliable connection between your computer and phone bad things could happen. Once the phone is plugged into the USB port of your computer/laptop try not to move the phone/laptop too much (could interfere with the connection)
If you get a "Wrong Device" error when trying to flash the phone, and you are 100% sure you do in fact have the Sprint LG G3 (LS990), replace the Sprint DLL file with the Generic LG G3 DLL file in the OP. This error is most common if you have changed the Product Name, Product Model, Display ID, and/or Build ID entries in the build.prop
If you get any COM errors make sure you did indeed switch the LGE AndroidNet USB Serial Port to COM41
How to Get your MSL/SPC
**NOTE** This will only work if your phone is able to turn on
Make sure you have the LG Drivers Installed on your computer (link is in 1st post for that)
Open up your dialer and enter ##DIAG#
Enable DIAG Mode
Connect your phone to your computer
On your phone change the USB Connection type to Charge Only (pull down your statusbar and click on USB Connected)
Download CdmaDevTerm on your computer(I prefer this version)
Extract the CdmaDevTermZip
Inside the extracted folder double click on the cdmaTerm file to start the application
On the right hand side of the CdmaDevTerm screen select "Scan ports"
Next select the LGE AndroidNet USB Serial Port from the drop down menu (mine was COM6) then click Connect
In the SPC/Lock Options change NV to LG from the drop down menu
Now click Read SPC
Success!
Took me all day to figure this out. I Was hoping someone would make a thread like this in the sprint section.
Very well done. Thank you!
Wikd said:
Took me all day to figure this out. I Was hoping someone would make a thread like this in the sprint section.
Very well done. Thank you!
Click to expand...
Click to collapse
Yea I checked with a moderator to make sure it was OK because there is a universal Restore thread for the G3 but not a lot of people know about it
Do you see anything I missed in the OP? I quadruple checked it but since your memory is fresh from the experience I figured you may have some more useful tips for the community
fergie716 said:
Yea I checked with a moderator to make sure it was OK because there is a universal Restore thread for the G3 but not a lot of people know about it
Do you see anything I missed in the OP? I quadruple checked it but since your memory is fresh from the experience I figured you may have some more useful tips for the community
Click to expand...
Click to collapse
I only made it to the point where I selected the tot and dll, and changed my com port. I stopped just before I was supposed to hit the yellow arrow. I was really just trying to make sure I had it all figured out for when I need it.
However, your instructions seem to be spot on. I did see a typo that I was going to point out to you but can't find it now, haha. You must have found it.
Thanks :laugh::laugh::laugh:
HELP!!!
so i did a big no no and changed my build prop and now i am stuck in a boot loop. this method isnt working because it thinks my model is different. any ideas on how to fix it???
FYI... I edited my build.prop dpi the other day. And got bootlooped ...I used the same method as this one on my G3spr LS990 AND WORKED FINE. There are a few tweaks to GSM instructions...but seems OP has covered all of them. BTW Flashtool did error out at 93% but phone still booted after the mini Os step.
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
treezy26 said:
so i did a big no no and changed my build prop and now i am stuck in a boot loop. this method isnt working because it thinks my model is different. any ideas on how to fix it???
Click to expand...
Click to collapse
what exactly is happening...and what step ?
Sent from my LGLS990 using Tapatalk
matthew0776 said:
FYI... I edited my build.prop dpi the other day. And got bootlooped ...I used the same method as this one on my G3spr LS990 AND WORKED FINE. There are a few tweaks to GSM instructions...but seems OP has covered all of them. BTW Flashtool did error out at 93% but phone still booted after the mini Os step.
Sent from my LGLS990 using Tapatalk
---------- Post added at 11:22 AM ---------- Previous post was at 11:19 AM ----------
what exactly is happening...and what step ?
Sent from my LGLS990 using Tapatalk
Click to expand...
Click to collapse
Its failing because it tells me it's the wrong device. I changed the model name to sync with my gear 2 neo. Which is weird because it worked fine for a bit then I rebooted phone and it just boot loops now.
Sent from my SPH-L710 using XDA Premium 4 mobile app
You got everything covered,.Thank you
Where was this yesterday morn when I had to figure it all out. I found all the scattered info after I was done.
Thanks for posting this. ?
Warning
Do not modify Build.prop, you will soft brick your device. Wait until a recovery is Out. Just posting this as a clear warning. This Guide would have helped me big two days ago. Great info Thanks to OP again
treezy26 said:
Its failing because it tells me it's the wrong device. I changed the model name to sync with my gear 2 neo. Which is weird because it worked fine for a bit then I rebooted phone and it just boot loops now.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't understand all this build.prop editing for the Gear 2 Neo. I've used my Gear 2 Neo on my G3 since phone launch...month or more before root existed. There are tutorials on XDA how to get it working and again ROOT IS NOT REQUIRED!!!
treezy26 said:
Its failing because it tells me it's the wrong device. I changed the model name to sync with my gear 2 neo. Which is weird because it worked fine for a bit then I rebooted phone and it just boot loops now.
Sent from my SPH-L710 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would see if you can hook up to adb, either with the phone completely shut down or while it's rebooting and push the stock build.prop
Here's the stock build prop : https://www.dropbox.com/s/8b9hkqen9d19l9e/build.prop
I would try to mount the system as r/w first. So in adb shell enter this:
mount -o rw,remount /dev/block/mmcblk0p41 /system
After that try to use adb push to get the new prop into the /system. Just use a terminal/Command Prompt and CD into the folder you have the stock build.prop saved in and push it with
adb push build.prop /system/build.prop
Then back in adb shell fix permissions
chmod 644 /system/build.prop
fergie716 said:
I would see if you can hook up to adb, either with the phone completely shut down or while it's rebooting and push the stock build.prop
Here's the stock build prop : https://www.dropbox.com/s/8b9hkqen9d19l9e/build.prop
I would try to mount the system as r/w first. So in adb shell enter this:
mount -o rw,remount /dev/block/mmcblk0p41 /system
After that try to use adb push to get the new prop into the /system. Just use a terminal/Command Prompt and CD into the folder you have the stock build.prop saved in and push it with
adb push build.prop /system/build.prop
Then back in adb shell fix permissions
chmod 644 /system/build.prop
Click to expand...
Click to collapse
I tried that way before Flashtool. The problem is it's read only without root. If you root, then abd shell and grant root, then you can do that.
I may be wrong, but that's the issue I ran into.
engine95 said:
I tried that way before Flashtool. The problem is it's read only without root. If you root, then abd shell and grant root, then you can do that.
I may be wrong, but that's the issue I ran into.
Click to expand...
Click to collapse
So if you asked for su in shell it would give you an error?
I did some looking, I wonder if issuing these command manually would work. The phone needs to be plugged into the computer and then turn it on. As its turning on:
(1 @ECHO*off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
fergie716 said:
So if you asked for su in shell it would give you an error?
I did some looking, I wonder if issuing these command manually would work. The phone needs to be plugged into the computer and then turn it on. As its turning on:
(1 @ECHO*off
(2)cd /d %~dp0
(3)echo.
(4)echo Waiting for device...adb wait-for-device
(5)echo.
(6)adb -d shell stop
(7)adb -d shell su -c "mount -o remount rw /system"
Click to expand...
Click to collapse
Yeah. It would say read only.
That's following what you have in the post above this one, just adding su before all the commands.
What you have posted here may work. I'll admit, my adb skills aren't that great.
bhint15 said:
I don't understand all this build.prop editing for the Gear 2 Neo. I've used my Gear 2 Neo on my G3 since phone launch...month or more before root existed. There are tutorials on XDA how to get it working and again ROOT IS NOT REQUIRED!!!
Click to expand...
Click to collapse
I used the build prop trick because it allows me to use everything such as s voice and download apps from the samsung store that's not available with just the gear manager app. I know it was a dumb mistake to change it since there is no recovery available yet. It worked fine for about an hour. I downloaded several apps for the neo just fine. Its when I changed a setting in xposed that needed a reboot to go into effect when everything went bad. I followed the steps here in the op to a tee and kept getting the red failed message after pressing the arrow. Didn't understand why till I read the error and it says wrong device. And that's when it clicked. Being stupid and impatient now I'm stuck with a bricked device. I don't think adb will work since it won't recognize it being Lg. Oh well thanks for you guys help. Luckily I'm still under warranty and have insurance. Do you think I will have issues with sprint since having it being rooted and change the build prop?
Sent from my SPH-L710 using XDA Premium 4 mobile app
Break screen? Dont know never carried warranty on a phone or used a factory warranty so im no help.
Sent from my LGLS990 using XDA Free mobile app
The multi user and guest account feature is not available on either of the two recent releases of Lollipop for the Z3v. I did some research and it appears this is the case, not only on other Verizon handsets like the Droid Turbo and the Galaxy S5 / S6, but a few other non-VZW devices as well. I'm not sure why it was removed but apparently it's just hidden. It can be enabled and I followed the instructions for doing this for the various other devices and can report that it works for our Z3v (see attached screenshots).
I've kind of cleaned up the instructions and put them below. Usual disclaimer - I'm not responsible for anything that may happen to you or your cat if you choose to do the following. You DO need root access to edit and write to the system file.
** To be safe, please make a backup of your phone and/or a copy of the build.prop file that you are going to edit.
Get ES File Explorer. Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)
With ES File Explorer, go to device/system/ and find the file: build.prop
Choose to edit it with ES Note Editor.
Scroll to the end of the file and type in the following:
fw.max_users=5
fw.show_multiuserui=1
Save the file.
I'm not sure if the next step is required but it was in half the instructions I saw, and I did it myself: Click and hold the file, go to Properties, and then change the permissions to Read, Write & Execute. [all three]
Reboot your phone.
When you're up and running, access multi user mode by pulling down your notification shade and then clicking on your user icon at the top right corner.
Notes so far:
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Therefore, an app such as Movie Creator can and will create a "highlight" movie that is composed from photos that are saved on the external SD Card. Just keep this in mind as far as privacy.
There is a per user option that lets you decide whether or not the additional users can use the phone and access the text messages. If you disable this ability, while they cannot open the phone app to make a call, the CAN receive an incoming call.
You can find out more about the nuances of additional users with your Google Fu.
Enjoy!
Wow! Great work!
AddictedToGlass said:
Wow! Great work!
Click to expand...
Click to collapse
Thanks! I really wanted this feature and it seemed like not many people care too much about it. It's my way of circumventing the awful permissions control we currently have in Android. That is, there are apps I want to use but refuse to install because of their overreaching permission requirements (contacts, etc) and so I can now create a second user with a new "dummy" Gmail account that has no sensitive information and install these apps without worrying.
By the way, something neat I figured out about this. Additional user accounts are not allowed to side load apps (the toggle to install from unknown sources is grayed out). I figured out that if the main user / owner restores an app through Titanium Backup, any other currently existing user will have it installed for some reason. I don't know why this happens but it's a neat glitch that gets you around that restriction.
Well I think most people simply don't let others touch their phones and so don't have a use for multiple user accounts. I find that my phone, as big as the screen is, is becoming more and more of a computer / tablet replacement. I like the idea of a multiuser functionality, but mostly to hide my own stuff. I'll silk never let anyone else touch my phone!
The use for multi-user that I've seen that makes the most sense is people with children. They will create a user profile for the child so they can't get into any of the parent's stuff or settings. That or the guest profile which will let them do whatever the heck they want without screwing up the phone.
Aside from that I have read that devs find the feature very useful for testing. Heck, that's not a bad idea to install and test apps, in general.
uh oh.
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
rpelljr said:
Well something didnt work. Maybe a certain build I have to be on or what. I followed the instructions to a t. Now stuck on endless boot loop. Only bad part is I'm on as hotel room working out of town without a laptop Or pc to fix it. I used a one click root just today and didn't install a proper recovery. Any thoughts
Click to expand...
Click to collapse
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Tigerhoods said:
I had a problem with this also twice cause I'm always doing stupid things to my phone my guess is you didn't change the system to r/w but modified it anyway or you used a editor that would let you input the correct values I used s manager I think. As far as getting your phone working you could try safe mode or maybe a factory reset if you can hold power and the volume button down and enter recovery.
Click to expand...
Click to collapse
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
rpelljr said:
I believe the mistake was made when i changed the permissions per instructions. I finially got to my house and im using adb to freeze the loop then going to push a script over to fix the permissions. I will update when i get it done and I will post my fix. Also I used ES file explorer, which i have already used it for years now. Never had anything like this happen before. it just baffles me. I have never got any instructions off of XDA that led to any malfuntion of my phone. But oh well, sh!+ happens.
Click to expand...
Click to collapse
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
it is guys if done right your system needs to be switched to r/w then go back to r/o after modifying the build prop if you modify in r/o you will get bootloop to a hard brick it depends.
Jurassic Pork Fried Rice said:
Hey! I'm so sorry! I got a couple of new phones (Droid Maxx 2 and LG G4) and have been using those phones so I haven't been checking these forums like I was when I just had the Z3v. Really sorry to hear that you ran into that kind of trouble . Thing is, the instructions above are culled from 4 or 5 different sets of instructions for various devices that I found across the web. I performed them step by step myself while cross referencing them to each other and combined them all to the instruction set above as I did it. Did you ever fix it with the method you mentioned? I'm curious if it was the permissions thing (odd, because it worked for me).
Click to expand...
Click to collapse
Well I kinda fixed it. I went and bought a HTC M9. Lol but not yet, I'm still working on it. I have found scripts to run, even a specific build.prop fix to push, but I have windows 10 and couldn't get adb to find the device. Plus I'm a little rusty. So I broke out my old windows 7 laptop I have used just for rooting an modding phones and tablets. I did get adb and fastboot to find it once. Then some reason lost it. I didn't have it ready to go. But I'm almost 100 percent sure I can get it. Just need to play around with it a little bit more. Having trouble with drivers etc. I will let you know when I have it.
And didn't really hurt my feelings getting the phone I truly want. I never had problems with HTC since I was flashing roms on my old window phones. I just want my pictures I cannot replace.
"Run it and enable Root Explorer setting. (You may be able to use any file explorer and editor with root access but this is used most in the instructions and works.)"
Alas- I am not rooted, and therefore can not enable "Root Explorer" option. Unless someone has some other suggestions- I think I can't do this unless I'm rooted.
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
AddictedToGlass said:
Well this is probably what I did to brick my first z3v.
I don't suggest anyone do this at all. There does seem to be an issue with the permission setting on the build.prop file. If it's not reset correctly after editing, you'll get stuck in a loop or worse. I'm stuck in bootloop, but can get into recovery. I made a backup hoping to learn how to edit the build.prop (delete it and rename the copied original to set it back as it was). But I can't even run the original zip that GigaSPX made up for us. (I don't have a backup like I hought I did.)
Anytime I try to install the flashable prerooted zip it tells me it's done after 2 seconds and says;
set_perm: some changes failed
I'm typing this on my z2 tablet, which has the multi user feature enabled. I'm going to see if RootExplorer will give me some clues as to why this doesn't work.
In the mean time I'm hoping someone can help me out?
If love to get this feature to work, but it has to be safe.
Just checked the build.prop on my tablet and got no clue.
Click to expand...
Click to collapse
a backup usually means going into your twrp and hit the back up button and make a copy of your system including data and all that. This is mandatory before messing with the build prop. If you want Pm me your build prop and I will send it back to you. With multi user enabled.
Yup, I know what a back-up is and how to do it, and I know it's a must before messing with the build.prop. I just really thought I had done it recently...
-and I had! But I forgot that a few days ago I bought myself a Christmas present; a 200 Gb micro SD, and copied most of the contents to the new card from my old one. I chose not to copy the backup because I had planned to make some changes and create a more recent backup. Never happened though because I got side tracked loading music and such. Lol!
So I'm all back together, but would still like to play with this feature. So I'm going to give it another shot.
A guest user does not have access to the original user's files on the internal drive - the guest user has their own file directory. The guest CAN access the External SD Card, though.
Click to expand...
Click to collapse
Perhaps the wrong thread but: enabled multi user on a Cube T8 only to find that guest and other user can access INTERNAL sd but not external sd. I'd rather have it the other way round. So the kids (other users) can use the whole of 32 GB sd card rather than me having to share the small internal sd with them.
Any ideas how to fix this? Phablet is not rooted btw.
got bootloop..... but i'm safe as i've backup.... through recovery..
I've inserted two lines and fell in bootloop
Thanks bro.. working....!!!! but second step is not needed...