yashsingh1/xdaforums huggingface dataset:
[G3 General] EEngineer:
This does not work. Do you mean press the home navigation button and volume down?

Power button + volume down takes a screen shot too.

_______________________________________

Sent from my G3 using the XDA App. Please excuse my brevity.
[G3 General] xRamz:
The long press back button dual window works for me...
[G3 General] corrsea:
+1
[G3 General] fye85:
Long press home button ll enable Google now (if turned on)
[G3 General] 573W1E:
Placing the G3 down to wirelessly charge while the screen is unlocked, then dismissing the wireless charging message before locking the device by tapping the status bar greatly improves the reliability of wireless charging so that it wont beep or error later on
[G3 General] veronesi.n:
In Music Player:

Songs/albums are sorted in small categories with a letter: "a, b, c,... "

Simply tap on a letter it will collapse without showing songs/albums... Usefull for fast browsing...
[G3 General] Swizzle82:
While using a browser you double tap to zoom except on the second tap hold and slide your finger downward you can zoom in to the level you like. chrome/stock I've tried it on.
[G3 General] Helloworld294:
You can add and delete widgets off the lock screen by pinching out and then sliding around, just like cm11.

You can make phone snappier by enabling "Force GPU Rendering" in Developer Mode settings.

You can disable Knock On/Off capability by downloading "Any Cut" app and making a shortcut to the hidden "Knock" menu.
[G3 General] aussiewan:
On the home screen, if you pinch to zoom out, you can then trash the LG Health / Tips screen. By zooming out again, you can press on the first panel to add the panel back in all it's "glory".
[Galaxy Note 3 Q&A, Help & Troubleshooting] RoidGalaxy:
Howdy fellas,

I used to have HotSpot on my "stock" phone before then I updated my phone to KitKat and I had totally forgot about the HotSpot setting.

So I need your help. I rather not root my phone but if thats the only choice I have to get HotSpot unlimited data then that's fine.

So this is what I have

Under Access Point Names

-APN -> fast.t-mobile.com

MCC -. 310

MNC - 260

APN type - default,mms,supl,hipri,fota,dun

APN protocol -> IPv4

and I'm using HotSpot Toggle widget

I have all these settings for it to work but it hasn't. If I have left anything out I'll provide the info needed to get this working.

Carrier is T-Mobile and its Note 3

thanks
[Galaxy Note 3 Q&A, Help & Troubleshooting] RoidGalaxy:
bump
[Galaxy Note 3 Q&A, Help & Troubleshooting] vndnguyen:
First, please make sure your APN settings is correct by checking the connection to the Internet.

If you are not sure about APN settings, you should ask your service provider (or your mobile operator)

Once you can access to the Internet using this APN, you can easily active the hotspot.
[Galaxy Note 3 Q&A, Help & Troubleshooting] RoidGalaxy:
vndnguyen, thanks for the reply...

It works but I want it to bypass T-Mobile hotspot limit without them knowing. Before when I had the settings correct it wasnt affecting the Data but now it is.
[Galaxy Note 3 Q&A, Help & Troubleshooting] RoidGalaxy:
bump... is there any threads on this subject. if so please provide a link...ill appreciate it.
[Upgrading, Modifying and Unlocking] steadfasterX:
History / Changelog

Previous development (v2.7.1.0)

I HIGHLY RECOMMEND USING v2.8 instead of this version!

You have been warned.. If you still want that buggy version go on here:

USE THAT ON YOUR OWN RISK! I STRONGLY RECOMMEND TO BACKUP EVERYTHING BEFORE PROCEEDING.

Working:

Install (to flash a custom Kernel)

Mounting partitions (see known issues for the internal one)

Reboot Recovery | System

adb shell

File Manager

Terminal Command

Totally untested:

WIPE (may work)

Known issues:

If the device becomes locked and then unlocked by the user adb will restart on the device (or crash and start again. haven't had looked into that yet)

When you use the "Power Off" option in the "Reboot" menu the device will reboot instead of powering off

RESTORE (will NOT work!)

BACKUP (will NOT work!)

You cannot mount the external sd via USB or MTP

Vibration is not working (I will not fix that atm because I like it that way)

Timezone is not set correctly (that seems to be a well known bug in several devices using TWRP....

Internal storage is missing (/data/media)

Hardware keys at bottom doesn't work

If you use the factory reset button /data partition will be inaccessible and need to be re-flashed (means you will LOOSE your app and system configs when you use factore reset)

Download:

Attached you will find the loki'ed TWRP version (v2.7.1.0):

AGAIN: THIS IS A PROOF-OF-CONCEPT only. It definitively WILL have bugs and problems! I want to proof that it will be possible to have TWRP on this device and also have a way to boot up into TWRP without booting the whole system.

twrp_2.7.1.0_recovery_FRoff.img.lok = FactoryReset is disabled / TWRP will be loaded instead

twrp_2.7.1.0_recovery_FRon.img.lok = FactoryReset is enabled / TWRP can be reached with "adb reboot recovery" only

Read the Installation & Usage instructions in the OP on how to install that file.
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
Awesome work! Saves having to risk modifying the bootloader (for now). :laugh: :highfive: Thanks!
[Upgrading, Modifying and Unlocking] eriklion:
I'm unable to get logs from TWRP, it does crash reliably when messing about in settings and such.

Timezone fix is needed. (Devices time is set to the correct local time, but TWRPs timezones arent correct.)

Device does not show internal storage.

Wipe menu does not differentiate from internal storage and /data

there's no /mnt, /storage or /sdcard present while in TWRP.

Uhm, I'm sure there's some more I've missed, but that's all I've got for now.
[Upgrading, Modifying and Unlocking] steadfasterX:
Uhm what do you mean? adb shell and then open /tmp/recovery.log? Clicking on the small mini icon at middle bottom of the screen? Both working for me. Have you tested the above attached version or the one I gave you at dropbox? The above is a more current one!

hm I will look into that

yeah forgot to mention that. Is that shown in CWM btw?

Could you explain what does that means?

/mnt and /storage are not needed or am I wrong? /sdcard would point to the internal storage I think but I decided to use /external_sd instead which is accessible in the latest version.
[Upgrading, Modifying and Unlocking] steadfasterX:
Yes.

There are several things coming in place when it comes to backing up out of TWRP atm...

You hopefully have read the big fat red warning ;) ? What I mean is the part regarding /data gets lost when you do a factory-reset

That said if you have entered TWRP by pressing the physical keys your /data partition will be wiped (really bad thing but that it is made for and I haven't had the time to look into that further)

The result is a cleaned /data which is not mountable until you format it with mke2fs.

(e.g.: "adb shell mke2fs -T ext4 /dev/block/mmcblk0p15")

If you do not do that what MAY happens is that TWRP failing because of missing /data (and if not then you should ensure that /data was really backed up)

But as your log told me it seems to be not the problem here 'cause the /data partition is detected by TWRP. so it could be 2)

Mounting points.

As stated the mount points are not fully working in TWRP atm. That means when it comes to /sdcard which is the internal device storage it will fail, too because it cannot be found. The reason for this is that LG mounts /sdcard by the sdcard service but that is somehow tricky thats why it is not working atm.

And on top: the internal storage normally needs to be mounted to "/data/media" especially when we want to use MultiROM later.

So +1 for /sdcard or/and internal storage related

background info: http://teamw.in/DataMedia

The last one I could imagine is "something else" ;) which could be catched by "/proc/last_kmsg"

The important thing is that this file gets written only after a crash and when the battery was not removed. So if the device reboots to TWRP again try to adb shell to the device and then paste the last_kmsg again. Maybe we can find something here.

When I will continue on TWRP I think of upgrading to v2.8 because they enable MTP here which could be good for copying data between device and pc..

BTW:

I have no idea what CWM port which is also be available would do in case of starting a backup especially what will REALLY gets backed up!!!!

IMHO the best way on doing a nandroid backup atm is "adb shell dd ...." :p Takes a long time but then you can be sure. I can give you all the mountpoints if you need them.

As I currently have not such much success with porting the ROM I will now come back here to TWRP and will finish it to have a hopefully fully working recovery. I cannot say the timeline for this but it will definitively be the next what I want to do because when this is done I can better match the rest for the ROM.
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
This should work (I've done it before for eriklion):

adb shell
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/storage/external_SD/system.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/storage/external_SD/boot.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/storage/external_SD/cache.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/storage/external_SD/userdata.2014-11-12.img

Now, is there a recommended adb command to wipe data and cache, since factory reset function is not the best choice? I see a few with the following process...

adb shell
su
format DATA
format CACHE

...but not much commentary on it.

I appreciate the second (third, whatever you are on) crack at TWRP. Hopefully the next version will squash the bugs. Btw, I will see if I can provide a /proc/last_kmsg tonight have posted a last_kmsg here.
[Upgrading, Modifying and Unlocking] steadfasterX:
yes thats all you need to backup & restore

I always do it that way:

Starting TWRP
adb shell
("su" in TWRP not needed normally)
mke2fs -T ext4 /dev/block/mmcblk0p15 (for userdata)
mke2fs -T ext4 /dev/block/mmcblk0p14 (for cache)

Then you can be sure it is clean and well formatted. ext4 is for both cache and userdata and works fine for me.
[Upgrading, Modifying and Unlocking] steadfasterX:
twrp v2.8 with many enhancements and fixes is on its way :D

Stay tuned ....

if you get bored in the meanwhile ... click thanks ;)
[Upgrading, Modifying and Unlocking] steadfasterX:
Is someone here with running the stock ROM (or absolutely not modified means formatted! /data partition) who is willing to give me a quick help? It must be stock or placed back to stock by using a backuped image dump if you have one.

The following need to be done in recovery so you need to have CWM or TWRP installed. Boot into recovery (adb reboot recovery) and then use "adb shell" to connect.

I need your output of this command:

mke2fs -n /dev/block/platform/msm_sdcc.1/by-name/userdata

This will not do/destroy/modify anything.

It should display some information about that partition. Read the details here http://linux.die.net/man/8/mke2fs

The reason is that LG factory reset seems to wipe superblocks (wanted by LG or not - fact is that they are thrown) and THEN forwarding to the recovery tool like TWRP but to be sure I need the above output from 1 or 2 people to be sure enough on how to proceed.

Thanks in advance

As Joel investigated that may destroy /data cause of a buggy version of mke2fs!! Oh man..

-----
[Upgrading, Modifying and Unlocking] steadfasterX:
Ok thx to joel I'm able to investigate the LG facotry reset further.

In parallel I will try another way which will be (if I get it working) absolutely smooth and will not have such workaround character like the current idea (hijacking factory reset).

Give me some time but if that works it would be a great solution for accessing recovery..

Stay tuned some good things may happen...

-----
[Upgrading, Modifying and Unlocking] steadfasterX:
Finally v2.8 for F3Q has arrived !!! I think a very good approach now!

Have fun ;) and as usual any thx click.... and so on

Check out the OP for Download and details:

http://xdaforums.com/showpost.php?p=55239027&postcount=1

UPDATE:

I have completely reworked the "Installation & Usage instructions" section in the OP. PLEASE READ and be happy ;)
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
Great work.

Am looking at method two. If I was to install a ROM, wouldn't the boot partition (thus my new recovery) be overwritten by the ROM package's boot.img? And when I was cooking with the Kitchen, the ROM required a specific mount point for the boot partition. If it is supposed to point to recovery, seems to me that neither would boot (overwritten recovery, ROM pointing in the wrong location).

So, what is this solution getting around? So we have an option to load TWRP before a system we don't necessarily trust will boot? Thus avoiding the bootloader fallback even more? Or is it a broken boot.img breaks TWRP as well so even if we try to go in through the bootloader, TWRP fails to load as well?

Sorry for my confusion, still trying to grasp all this new information.
[Upgrading, Modifying and Unlocking] steadfasterX:
Thanks :D

Method 2 will suggest that if you install a custom ROM that you are be able to use/choose the boot.img partition (I hoped that the "hint" at the was clear enough but better to ask of course!)

Well yes you either need to point to the recovery partition or (and that would be what I recommend) you let the user choose what he wanted to do.

The best we can do here (and that is what I will do for my custom ROM if I get it done some day) to use AROMA installer and ask the user if he has a recovery installed in the boot partition or not. Then you can choose what to do in the updater script.

I uploaded an example of my AROMA installation setup for the "sediROM for Samsung Captivate Glide" in this post. This one is VERY complex but you will get the idea and many input on how to do things.

Yes using method 2 we have always coming TWRP up when powering on the device. We then can choose to do things in there or to boot to "recovery" which will be the ROM. What do you meant with "bootloader fallback"?

Not sure If I got you. When the boot partition gets overwritten TWRP and any possibility to get into TWRP will be lost because it sits only in the boot partition when using method 2. If you choose to do a factory reset when powering on the device or from within the ROM I have no idea what happens then unfortunately. That is untested but if you willing to test..

No worry about that ;) happy if that is useful for someone
[Upgrading, Modifying and Unlocking] OfficerJimLahey:
Thanks! I will take a look at this in the next few days.

Bootloader fallback as in having to access TWRP via the bootloader. Our regular method is to access form the ROM, but if the ROM is bricked for whatever reason, the fallback is through the bootloader.

I was alluding to the scenario if one was to choose method one, installed a ROM, and things got busted badly... Would you even be able to access TWRP with a bad boot partition? I think so, because recovery partition should be self sufficient (I think you proved it by swapping their places by way of method two), it is just getting into recovery by way of bootloader) I don't particularly like.

Had to face that fear last night, and ultimately, TWRP started up fast enough from the bootloader that it seemed like nothing happened, but when i went to dump the log, it could not recognize the sdcard. DD'ing my userdata partition back fixed that issue.
[Upgrading, Modifying and Unlocking] steadfasterX:
You mean "factory-reset" right? By either pressing the factory reset buttons (or by choosing from within the ROM) correct?

If you install TWRP with method 1 and your boot partition gets corrupt you still be able to reach TWRP by using the factory-reset buttons. But you

will loose

/data then.

If you install TWRP with method 2 and your boot partition has gone you can not start TWRP anymore because it sits on there.

So you're more bulletproof by choosing method 1 because you would reach TWRP even when the boot partition gets damaged but you will loose /data then! Mentioned in the known issues in the OP.

When you have TWRP installed with method 1 you will reach TWRP by factory reset buttons and it will DO NOTHING ! Really! It simply starts TWRP because I patched TWRP that way that it will not wipe anything when triggered by the factory-reset command / button!

I can say that for double sure since today because:

1) In one of my tests I had disabled REALLY EVERY wipe option within TWRP - compiled it - installed it and even then /data gets lost!

2) I have installed the BOOT image means KERNEL on the RECOVERY partition today again and then used the factory-reset buttons again (after I restored /data of course)... and /data gets lost AGAIN--?!!

That means even when there is absolutely no custom recovery in place (like TWRP) which would normally handle wiping /data then nevertheless /data gets corrupted! I have tested that twice so I can say now for sure that this has nothing to do with TWRP but it comes from the LG bootloader instead! That bootloader is CRAP. sorry.

I had tested one approach which is build in boot image RAM disk which catches the keys which are pressed and then reboot into recovery. That would work but only as long as you have a working boot image partition. So that is the same good/bad as having TWRP sitting within the boot partition which is much easier to do so I decided to go this way for now.

One last word about the crappy factory-reset by LG: I have tried a lot to find out what really happens to the partition or partition table of /data when those keys are pressed but the only thing I can say is that the superblocks are inaccessible and the same for the backup superblocks. doing a "mke2fs -S" does not work (and wouldn't fix the root cause of the issue) and I have no idea what LG do here. Therefore cannot fix that ..

so I believe we will need to live with one of the 3 methods described in the OP....

Hope that answered some of your questions... :D
[Upgrading, Modifying and Unlocking] steadfasterX:
Bad news..

The Desire Z of my wife is completely broken now.

That means I cannot develop anymore..

- I ported and released the latest TWRP version to the F3Q

- I'm able to build AOSP JellyBean (not booting yet though),

- I compiled and released a custom AOSP Kernel (named sediKERNEL)

.... and a lot more..

I have everything I need to continue here in place...

I have the will and the ability to continue...

But no device anymore..

If someone has a F3Q to give away.. then I will continue but I'm not willing to buy a F3Q for developing only. So if you have an idea how we could continue let me know.

Update:

Check out the following link if you want to help http://xdaforums.com/showthread.php?t=2952919

Otherwise that will end here for me unfortunately...

Hopefully not.

Yours

Xdajog.

-----
[Upgrading, Modifying and Unlocking] steadfasterX:
I will update the installation instructions soon!

Because of the new sediKERNEL v2.0 the instructions will be made bullet proof only .. and i try to do it more detailed [MENTION=4270200]Kediil[/MENTION] ;)

-----
[Upgrading, Modifying and Unlocking] Kediil:
Thank you xdajog!
[Upgrading, Modifying and Unlocking] steadfasterX:
dupl
[Upgrading, Modifying and Unlocking] steadfasterX:
FAQ section including howto backup etc added!

Check it out: http://xdaforums.com/showpost.php?p=60832650&postcount=2

The guide to install TWRP will be re-worked soon, too.

Greetings

xdajog

.

--- update ---

Ok done! I removed, cleaned up and cleared some things within the OP, installation and usage instructions.

Also added another point to the FAQ.

hope that helps for everyone.

Greets

xdajog

.
[Upgrading, Modifying and Unlocking] Kediil:
So. I can't get TWRP on here.

I'm good up to

"mount -oremount,rw /system"

Then I've tried it a couple of ways.

I can do

"cp /..."

return

"loki_tool flash recovery /..."

and I get the error

'first argument must be "boot" or "recovery"

Or I tried it as a continuous line, error "unable to chmod loki_tool: no such file or directory".

This isn't rocket science, but I'm still failing miserably. I just don't get why.

I copied the cmd window in the hide here.

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices

List of devices attached

* daemon not running. starting it now on port 5037 *

* daemon started successfully *

C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices

List of devices attached

LG-D520-707c699 device

C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell

shell@android:/ $ su

root@android:/ # mount -oremount,rw /system

ki_tool /system/bin && chmod 755 /system/bin/loki_tool <

e/sdcard0/download/twrp_x.x.x.x_recovery_froff/off.img <

Loki tool v2.1

[+] First argument must be "boot" or "recovery".

ery /storage/sdcard0/download/twrp_x.x.x.x_recovery_FRoff/off.img <

Unable to chmod loki_tool: No such file or directory

10|root@android:/ #

Sorry to be a bother. I appreciate you a lot xdajog! The refresh is very nicely worded.
[Upgrading, Modifying and Unlocking] steadfasterX:
Well sorry... I will check this but the output you pasted seems to be damaged? The first parts seems to be missing of the lines or so. You do not bother but as you see I'm quite busy atm so i will come back in the next days. Thanks for your patience.

-----
[Upgrading, Modifying and Unlocking] Kediil:
SOLVED

HUZZAH

I finally got it to work.

To start, I had somehow downloaded the build5 file, and not the recovery file. I know it's silly, but a direct link in the actual instructions there to the file being used might be worth the moment. I don't know if maybe it wasn't clear before you tweaked, or if I just dazed out and took the 2.8 over the 2.7

Maybe I'm just CMD challenged.

To add, yours reads

"loki_tool flash recovery /PATH-WHERE-YOU-COPIED/twrp_X.X.X.X_recovery_FRoff/off.img"

when I had to input

"loki_tool flash recovery /PATH-WHERE-YOU-COPIED/twrp_X.X.X.X_recovery_FRoff.img.lok"

That.. was way more brain power than *ever* needed to go into this. Hopefully it's smooth sailing from here.
[Upgrading, Modifying and Unlocking] Infran:
Help getting ADB working when booted into TWRP

Heya. So I've been trying to do Bulletproof Method #2. I got TWRP flashed to the recovery partition, but I can't seem to get ADB to work when booted into TWRP. I tried waiting for the screen to turn off as suggested under the workarounds, but ADB still doesn't detect my phone (when I enter 'adb devices', the output is blank). It doesn't matter whether I'm under the 'ADB Sideload' feature or just on the menu screen.

I tried making sure ADB is up to date and making sure my phone's drivers are installed properly. The only change was that I could actually use 'adb reboot recovery' instead of having to use an app.

Google doesn't seem to turn up much else. Any suggestions?
[Upgrading, Modifying and Unlocking] steadfasterX:
Hi,

first of all: tell me your operating system and version please.

(On Linux you may have to add an udev rule and on Windows you may need to update/install another driver)
[Upgrading, Modifying and Unlocking] Infran:
I've primarily been using Windows 8.1 64-bit for my phone, though I do have access to Ubuntu and Mac OS Yosemite (though I haven't figured out how to get ADB to work on Mac).